Description: Gradient backgrounds of slides are not preserved when the presentation is saved as PPTX with LibreOffice Impress. Steps to Reproduce: 1. Create a new presentation in LibreOffice Impress. 2. Click on Slide > Properties, and change the Background to Gradient. 3. Save the file as PPTX and reload it. Actual Results: The gradient background of the slide gets lost. Expected Results: The gradient background of the slide should be preserved. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 148821 [details] A presentation with a gradient in the background.
Created attachment 148822 [details] The same presentation exported as PPTX.
Created attachment 148823 [details] A screenshot showcasing the issue.
Thank you for reporting the bug.I cannot reproduce this bug. Gradient backgrounds of slides are preserved even after saving as PPTX. Version: 6.3.0.0.alpha0+ Build ID: b6b28931435e44aca92b8c0e1659f701e3ed1a87 CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-01-30_06:57:04 Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Repro with multiple versions back to 3.3.0. I tested from from scratch. Weird that I could not find an older report!
Hi, Actually Bug 111742 is about the same thing. The problem exists not with the default gradients but with customized gradients (and patterns). Would be great if somebody would start to take care here! Regards Martin
(In reply to martin651 from comment #6) > Actually Bug 111742 is about the same thing. The problem exists not with the > default gradients but with customized gradients (and patterns). > > Would be great if somebody would start to take care here! It is not about the same thing. If it was, you would not see a gradient in attachment 148821 [details]
No longer happening in Version: 6.4.0.0.alpha0+ Build ID: f4f8bccbd4e2c3979a83d5b2f49e16a99a3a2016 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Dupe of bug 127379 *** This bug has been marked as a duplicate of bug 127379 ***