Hello, I use Impress in Libreoffice 5.2.5.1 under Ubuntu 16.04. - I create several dias, based on the "green" master page and give them a title, and fill in the object area of each dia with a few lines (level 1) - I edit the master page "verdoyant" to modify the filling of the title area and the filling of the area of objects. - I then assign another master page (DNA) to a few dias. - I also edit the master page "DNA" to modify differently the filling of the title area and the filling of the area of objects. This is where it stalls: - at the level of the filling of the titles, no problem. - But the filling of the dias of the DNA PM kept the filling that had been defined in the verdant PM. - If then, I modify the filling of the object area of the Verdant PM, this affects all the dias. - Finally, on the dias based on the DNA PM, if I right click on the objects area, and I choose "default formatting", this dia finally has the right filling. Conclusion: it seems that there is a bug in the filling of the object area when changing PM: The old fill of the object area is applied directly to the dias for which the master page is changed , And these dias no longer follow the filling of the new master page. NOTE: What I said for filling the object field is also true for the line properties of this zone. But there is no problem with the fonts in this area. I have found no way to get around this problem. (Except to return to each dia, select the object area (s), and apply "default format".) And I've been looking for several days ... Does anyone see any other solution? Otherwise, it seems to me that this would be a bug. Just another information: I tried under Windows 7 Libreoffice 5 (may be 5.1.6, but not sure of the minor version) and had the same problem.
(In reply to Christian from comment #0) > - I then assign another master page (DNA) to a few dias. Please attach an example file that is at the point of this step. This is to make testing faster. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the document.
Created attachment 133107 [details] PPS file Hi, during the creation of a file showing the problem, I found a closer approach of the problem: explained hereunder: - I create 4 dias, based on the "Verdoyant" master page and give them a title, and fill in the object area of each dia with a few lines (level 1) - I edit the master page "verdoyant" to modify the filling of the title area: background color Yellow2; font bold and Blue2. - I modify the filling of the filling of the area of objects: background color Blue2; font bold, Italic and Blue2. - I save that master page. Before saving, I see this result: - Slides 1 is correct and follow characteristics of master page "Verdoyant". - Slides 2, 3 and 4 are not correct: they follow characteristics of master page "Verdoyant", except for the filling of the area of objects which remain unchanged. After saving, closing the file and reloading it everything is correct... So the problem seems to be: when changing the filling of the area of objects in a master page, the change take effect only when opening the file again. It is not possible to send you an odp attachment showing the problem. However, When the problem occurs, if i save the file as pps before closing the file, the pps file is affected by the problem. I send you the pps file in this attachment, and open an other comment to sent the odp file
Created attachment 133109 [details] The odp file see previous comment: this comment was to attach a second file to that comment.
Created attachment 133115 [details] PDF export of ODP Is this really correct? The ODP does not match your description. Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha1+ Build ID: 6e4cba99bb35e6697b94309eedd1a08ebea2dc68 CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on May 5th 2016
Yes, it is correct: As I explained in comment 2, "After saving, closing the file and reloading it everything is correct..." That means that saving the odp file fixes the bug... And the odp file I sended has no longer the problem. It is why I saved first as pps before saving as odp... And you can see the problem on the pps file. Even if saving as odp fixes the problem, it remains a bug: all other fields don't need "saving as odp" to apply the changes on the slides. I hope this will help.
Ok, steps: 1. Create new presentation with Lush Green master 2. View - Slide Master 3. Select the main text box and change the area fill to yellow color 4. Add a second slide so you will see the yellow 5. Add a third slide and apply master DNA from the sidebar See that the Slide pane preview shows it correctly, but the edit view shows the text box fill as yellow. (Saving and reloading fixes the problem) Arch Linux 64-bit, KDE Plasma 5 Version: 5.4.0.0.alpha1+ Build ID: 6e4cba99bb35e6697b94309eedd1a08ebea2dc68 CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on May 5th 2016 Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Created attachment 133137 [details] comment 7 ppt file Thanks Buovjaga, I tried ther 5 steps you suggested in comment 6... After step 5, my slide3 had the layout of master DNA, but with yellow text area. So the problem is already present. I added a step 6: changing master DNA, with blue text area: it gave apparently no change on slide 3 (text area was always yellow) I saved the file successively in ppt, pps and odp, then closed the file. Opening the pps or ppt file give slide 3 in yellow Opening the pps file give slide 3 in blue. (It seemed yellow when saving the file.) I attach the 3 files: test2.ppt, test2.pps, test2.odp.
Created attachment 133138 [details] comment 7 pps file
Created attachment 133139 [details] comment 7 odp file
** 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
Dear Christian, 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
Dear Christian, 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