Bug 128597 - Incorrect save of presentation - gradient background
Summary: Incorrect save of presentation - gradient background
Status: RESOLVED DUPLICATE of bug 125449
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.2.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-04 23:25 UTC by Antonios Prapas
Modified: 2019-11-26 11:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Antonios Prapas 2019-11-04 23:25:19 UTC 
When you create a new presentation, you add a new slide, then if you select the "Gradient" format as the background option, after you configure it with the colors you want you save it. When it's time to open the presentation again, you background colors have been set to black-white instead of the colors of your choice. So the problem is that whatever colors you set in this background format after you save the presentation and you open it again the colors are set to the default ones (black-white).
Comment 1 Xisco Faulí 2019-11-05 11:40:58 UTC 
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 2 raal 2019-11-06 22:07:42 UTC 
Works for me in Version: 6.4.0.0.alpha1+
Build ID: fa7f07d23de31e5f1660a643d83ca8a2e565f69c
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 


Please test with newer version. Thank you
Comment 3 NISZ LibreOffice Team 2019-11-26 11:49:50 UTC 
This situation was recently fixed as part of bug #125449

*** This bug has been marked as a duplicate of bug 125449 ***