Created attachment 110467 [details] Database for testing some charts in Report-Builder Open the attached database. Open one report. Only the report Report-Integer-Temperature would show a chart with content. All other reports will show empty charts. Works as expected with LO 4.2.0.0.beta2. Doesn't work with LO 4.2.8.1. Have no other version between this installed for testing. My configuration: OpenSUSE 12.3 64bit rpm Linux.
4.2.5.2 good, 4.2.6.2 bad bibisect range: abf842e4b125b9f863ea4c2af17ad6ac7d82b15e.. e990e4d145f16c0c7e4e9e12c4882ddde63a3d5a let's see, if we intersect the above ranges... reverting these commits on master gets the data points back on the charts: commit 2b959fb871a68f08a06850909abd16f71033aa3a Author: Kohei Yoshida <kohei.yoshida@collabora.com> AuthorDate: Thu Jun 5 15:17:00 2014 -0400 Commit: Markus Mohrhard <markus.mohrhard@googlemail.com> CommitDate: Fri Jun 6 01:09:43 2014 +0000 fdo#72727: Revert "-Werror=unused-but-set-variable second try" This reverts commit ccf7b15c0a5776c6431fdcb0c0e2b0f3935ae3dc. (cherry picked from commit 61d958f37ed2aad6be2eab7bb507e0fb77716eec) commit 5a53dfa86a2b61154f4c2c7cb356d32a569aaf69 Author: Kohei Yoshida <kohei.yoshida@collabora.com> AuthorDate: Thu Jun 5 15:02:48 2014 -0400 Commit: Markus Mohrhard <markus.mohrhard@googlemail.com> CommitDate: Fri Jun 6 01:09:28 2014 +0000 fdo#72727: Revert "fdo#68663 don't blindly force categories when there are" This reverts commit b090cbdf82e0827234caf5969124f6631311ef35. (cherry picked from commit 91ca3a92c54a08ad13497d7e8ac1916e7b68bbfd)
This is quite possibly the same bug "under the hood" as bug 68663, whose fix was reverted to fix bug 72727.
Adding self to CC if not already on
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Couldn't be tested with LO 5.0 or newer because reports with charts couldn't be opened. See https://bugs.documentfoundation.org/show_bug.cgi?id=92720 .
Marked as regression, see comment1.
Tested Robert's sample database with Version: 5.1.3.2 Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b CPU Threads: 2; OS Version: Mac OS X 10.11.5; UI Render: default; Locale: fr-FR (fr.UTF-8) The only report that displays data points is Report_Integer_Temperature, on the other reports no data points are displayed at all.
Isn't this a DUP of bug 68781 ?
Adding keyword 'bibisectRequest'.
Adding Cc: to Kohei Yoshida
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists with LO 6.0.5.2, OpenSUSE 42.3 Leap, 64bit rpm Linux. ... but also the Report_Integer-Temperature doesn't show any chart. See bug117162 for this ...
Dear robert, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug couldn't be tested, because charts aren't shown since LO 5.4.0.3. See bug 117162
Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
With master sources updated today (so including fix for tdf#117162), I could reproduce this. I noticed these logs: warn:xmloff:249169:249169:xmloff/source/chart/SchXMLTableContext.cxx:594: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:date-value value=2013-01-10T00:00:00.0Z warn:xmloff:249169:249169:xmloff/source/chart/SchXMLTableContext.cxx:594: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:date-value value=2013-03-10T00:00:00.0Z warn:xmloff:249169:249169:xmloff/source/chart/SchXMLTableContext.cxx:594: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:date-value value=2013-06-10T00:00:00.0Z warn:xmloff:249169:249169:xmloff/source/chart/SchXMLTableContext.cxx:594: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:date-value value=2013-07-10T00:00:00.0Z warn:xmloff:249169:249169:xmloff/source/chart/SchXMLTableContext.cxx:594: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:date-value value=2013-08-10T00:00:00.0Z warn:xmloff:249169:249169:xmloff/source/chart/SchXMLTableContext.cxx:594: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:date-value value=2013-12-10T00:00:00.0Z warn:xmloff:249793:249793:xmloff/source/chart/SchXMLTableContext.cxx:599: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:time-value value=PT07H00M00S warn:xmloff:249793:249793:xmloff/source/chart/SchXMLTableContext.cxx:599: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:time-value value=PT08H00M00S warn:xmloff:249793:249793:xmloff/source/chart/SchXMLTableContext.cxx:599: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:time-value value=PT11H30M00S warn:xmloff:249793:249793:xmloff/source/chart/SchXMLTableContext.cxx:599: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:time-value value=PT15H00M00S warn:xmloff:249793:249793:xmloff/source/chart/SchXMLTableContext.cxx:599: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:time-value value=PT18H00M00S warn:xmloff:249793:249793:xmloff/source/chart/SchXMLTableContext.cxx:599: unknown attribute urn:oasis:names:tc:opendocument:xmlns:office:1.0 office:time-value value=PT22H00M00S code pointer: xmloff/source/chart/SchXMLTableContext.cxx
Bug still reproducible with Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 040b3198fde3385e19e7380fdcabae84a0abac9d CPU threads: 8; OS: Mac OS X 12.2.1; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded
Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
On pc Debian x86-64 with master sources updated today, I could still reproduce this.