If I add a new Master, give it a background, delete it and create another one, the last one has a solid blue background.
Steps to Reproduce:
1. In Impress, go to View > Master Slide
2. Create a New Master
3. On the Slides panel, select the new Master
4. On the Properties panel, select Insert Image
5. Pick some image (tested with .jpg and .png)
6. Delete the Master
7. Create a New Master
The new Master has a solid blue background
The new Master should have the image as background
User Profile Reset: Yes
OpenGL enabled: Yes
This is related to https://bugs.documentfoundation.org/show_bug.cgi?id=101711
This bug is present in:
Version: 184.108.40.206.alpha1+ (x64)
Build ID: 93139c011411b0e48c5fc8d39fe9203f55c7ff0a
CPU threads: 2; OS: Windows 10.0; UI render: default; VCL: win;
Locale: en-US (en_US); UI-Language: en-US
and on versions 5.3.x.
It is not present in LibreOffice 220.127.116.11
In branch 5.2, 78ec0b2b (https://gerrit.libreoffice.org/#/c/29490/) fixes the bug.
Created attachment 151760 [details]
Created attachment 151910 [details]
I managed to fix this bug in branch libreoffice-6-2-4 by "porting" 78ec0b2b, but I'm not sure if it is the best solution...
However, as far as I tested, the fix doesn't cause regressions (the bugs described in https://bugs.documentfoundation.org/show_bug.cgi?id=125577 and https://bugzilla.redhat.com/show_bug.cgi?id=1353069 are gone)
Should I submit this to Gerrit ?
(In reply to Andrés Maldonado from comment #2)
> Created attachment 151910 [details]
> I managed to fix this bug in branch libreoffice-6-2-4 by "porting" 78ec0b2b,
> but I'm not sure if it is the best solution...
> However, as far as I tested, the fix doesn't cause regressions (the bugs
> described in https://bugs.documentfoundation.org/show_bug.cgi?id=125577 and
> https://bugzilla.redhat.com/show_bug.cgi?id=1353069 are gone)
> Should I submit this to Gerrit ?
Absolutely, other can check whether it's correct or not
Dear Andrés Maldonado,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assign it back to yourself if you're still working on this.
Dear Andrés Maldonado,
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!
Still rerpo in
Version: 18.104.22.168.alpha0+ (x64) / LibreOffice Community
Build ID: b438854a0b5148880e455cbeeff14d4e3d825711
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL Jumbo
(In reply to Andrés Maldonado from comment #0)
> Actual Results:
> The new Master has a solid blue background
> Expected Results:
> The new Master should have the image as background
I wonder why the expectation is to show the background of the deleted master slide again, I'd expect it to have the default white background, no?
I haven't checked which commit introduced this, but can confirm that in libreoffice-5-2 the reverts brought back the previous behavior.
author Caolán McNamara <email@example.com> 2016-09-30 12:45:03 +0100
committer David Tardon <firstname.lastname@example.org> 2016-10-05 06:47:34 +0000
Resolves: tdf#101711 revert attempt to drop unused bg images
(In reply to Aron Budea from comment #7)
> I wonder why the expectation is to show the background of the deleted master
> slide again, I'd expect it to have the default white background, no?
Exactly. In other words, creating a master slide should always default to color = None.