Bug 124690 - Renaming a master page does not update the "master pages" pane
Summary: Renaming a master page does not update the "master pages" pane
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
(earliest affected) release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Sidebar-Master-Slides
  Show dependency treegraph
Reported: 2019-04-11 13:36 UTC by Callegar
Modified: 2023-05-22 03:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Callegar 2019-04-11 13:36:18 UTC
Open a presentation, select the master pages pane in the sidebar in order to see the "master pages used in this presentation". Now move to the master pages view: view->master slide. From there, rename a master page. Note that the "master pages used in this presentation does not update". In order to have it update, you need to save and reload the presentation.

This is an issue because it may cause master page name clashes.

For instance, suppose that your presentation contains a master slide named "foo". You rename it to "bar". Then you copy a slide from another presentation having a different master slide called "foo". With this you end up with a master  pages pane showing two different "foo" master pages. At this point, if you try to apply the new "foo" master to some slide, you end up applying "bar" to it.

Steps to Reproduce:
See description

Actual Results:
See description

Expected Results:
See description

Reproducible: Always

User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: PresentationDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Comment 1 Roman Kuznetsov 2019-05-12 20:56:49 UTC
repro in

Build ID: 65f81f6acdeb03b34033a1c6515618936d5f8eca
CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: kde5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-04-23_17:18:14
Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US
Calc: threaded
Comment 2 QA Administrators 2021-05-12 03:58:59 UTC Comment hidden (obsolete)
Comment 3 Roman Kuznetsov 2021-05-21 19:43:49 UTC
still repro in

Version: (x64) / LibreOffice Community
Build ID: 58b0c95ad50139a62bddb348d10f94053c09cd5b
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
Calc: threaded
Comment 4 QA Administrators 2023-05-22 03:15:06 UTC
Dear sergio.callegari,

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