Description: Saving a chart with blocks that use hatching as PPTX (regardless whether the original came as PPTX or ODP) loses the hatching and replaces it with solid color. Steps to Reproduce: 1. Open sample document (in ODP format). 2. Save as PPTX. 3. Close and reopen saved PPTX. Actual Results: Observe the difference where what used to be blocks with hatching now show in solid color. Expected Results: Document does not visually change when saving as PPTX. Reproducible: Always User Profile Reset: No Additional Info: This originally came from a PPTX document, and the import from PPTX to ODP with LibreOffice seems to have worked just fine. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Created attachment 140295 [details] Sample document (in ODP)
Created attachment 140296 [details] Screenshot before
Created attachment 140297 [details] This is how it looks like after saving as PPTX and reopening that
On pc Debian x86-64 with master sources updated yesterday, I could reproduce this.
Also reproduced in Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Created attachment 147438 [details] The example file opened in current LO 6.3 A source of this problem is that there is a 0 line spacing set in the chart data series, but it is not displayed as such. A hatching with 0 line spacing is indeed a different way of saying "solid fill". Another angle is that in MSO it is not possible to select an arbitrary line spacing - this is hidden in the UI as a property of the preset patterns.
Created attachment 147439 [details] Exported pptx with newly set 0 line spacing If I try to set a 0 line spacing in a current LO version, the exported line spacing value is set to 0.05 cm and not a solid fill anymore.
Created attachment 147440 [details] Exported pptx with newly set 0 line spacing in PP and Impress LO no longer saves 0 line spacing to pptx, so it's not possible to export the solid fill instead of hatching.
(In reply to Gabor Kelemen from comment #8) > Created attachment 147440 [details] > Exported pptx with newly set 0 line spacing in PP and Impress > > LO no longer saves 0 line spacing to pptx, so it's not possible to export > the solid fill instead of hatching. Addition: the original file can still be exported with solid fill, but any newly created hatching with 0 line spacing cannot. Maybe we can live with that, and close this as WFM?
Dear Gerald Pfeifer, 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
Still there in Version: 7.2.0.0.alpha0+ Build ID: 35e471bb4d1388cf5afcdcee214cf5111edf44e3 CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-12-12_01:52:12
Dear Gerald Pfeifer, 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
Still there in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 01c9c971e43782800ebf63acc763a7e7fba096c1 CPU threads: 8; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US