Description: When non-default area/fill colours are chosen in a Pie chart in Base Report Builder, these colours revert to the defaults when the report is shown in Writer. Same thing happens when the chart is re-edited in Report Builder. Same thing happens in an Area chart. Using LO v5.2.6.2 (Build ID: a3100ed2409ebf1c212f5048fbe377c281438fdc downloaded from LO website on 30 April 2017) on OpenSuse 13.2 Steps to Reproduce: 1. Create new database in Base with 1 table with 2 fields and 3 records (first field = category labels, second field = values, no key). 2. Create report using Report Builder: insert pie chart using data from the table. 3. Change pie chart area colours other colours and save the report. 4. Re-edit the report and select the pie chart for editing: see the colours revert to defaults. 5. Exit Report Builder *without* saving changes. 6. Generate the report: see the colours in Writer have reverted to defaults. Actual Results: 1. On re-editing, chart colours in Report Builder revert to defaults. 2. Chart colours in Writer have reverted to defaults. Expected Results: 1. On re-editing, custom Chart colours remain as last specified. 2. Custom Chart colours are shown in report in Writer as last specified in Report Builder. Reproducible: Always User Profile Reset: No Additional Info: Simple test file piechartcolorstest.odb is attached which demonstrates this issue. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Created attachment 132973 [details] Test file to demonstrate that Pie chart colours revert to defaults in generated report
Could confirm the buggy behavior. You could change the color, but seems it switches to a default-value when executing the report. Doesn't work with any version I have installed, also 4.* and 3.6.7.2. So could be it has been inherited by OOo. Tested with OpenSUSE 42.1 64bit rpm Linux
** 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
(In reply to QA Administrators from comment #3) AFAIK, charting in LO Base v6 is comprehensively broken, so I can't test this bug in LO v6. I have tried most releases (from TDF website) since LO v5.3, and have found that charting in LO Base is broken in one way or another in all them. Running a chart report produces a blank space where the chart should be. Clicking on a chart in Report Builder (to edit it or check settings) likely crashes LO Base. So I am sticking with LO v5.3.6.1 in a separate install for Base reporting, which still works for me (well, works well enough). Text reports in LO Base v6 and previous versions work well. Report Builder seems a lot more stable than it was. So the regression with charts is disappointing - and hard to understand as there seems to have been no changes in LO Base functionality (nothing in release notes). I have experimented with scripts to recreate chart reports for each new LO release, because recreating the reports has resolved some issues in the past, but without success for charts. It seems to me that the issues are not in Report Builder itself but with the underlying API. Just to confirm that I am running LO from TDF on OpenSuse 42.3 x64.
Dear branestawm, 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
(In reply to Robert Großkopf from comment #6) > Bug couldn't be tested, because charts aren't shown since LO 5.4.0.3. See > bug 117162 Seconded. AFAIK, charting in LO Base v6 is comprehensively broken, so I can't test this bug in LO v6.
Dear branestawm, 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
Seconded (I agree with previous comment).
Unfortunately, testing 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 on Mac M1 Apple Macbook leads to either an automatic crash, or a systematic hang requiring force kill, when I : - change the colours in the segments of Pie Chart.odt, and then click outside the selected area (crash) ; - change the colours in the segments of Pie Chart.odt and then use the escape key to move out of the selected area, then "Save" (hang/beachball).
Dear branestawm, 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
(In reply to QA Administrators from comment #12) Bug persists for Pie Charts in LO 7.4.3.2 on OpenSUSE LEAP 15.5. This bug does not arise for me in Column or Bar Charts in LO 7.4.3.2 In general, LO Base chart reports seem to have improved somewhat in v7 onwards. However, Report Builder remains "flaky": it crashed several times today as I repeated this test with different chart types and colour combinations. So I am staying with my Basic "templates" for chart reports, which call the API directly and reliably. I regret I do not have time to test with the latest LO 7.6+, particularly as running different versions can cause difficulties with Java DB drivers.
Have tested this again: Have changed the colors and could execute the report with other colors. Saved the report and the colors, which now appear, will different to the default colors - but not the colors I have chosen. Seems the colors are connected in a wrong way, but would be saved. Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 6; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded