Bug Hunting Session
Bug 54894 - : Master Document Updating
Summary: : Master Document Updating
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2012-09-13 23:25 UTC by fonder25674
Modified: 2014-02-26 19:31 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 fonder25674 2012-09-13 23:25:32 UTC
Problem description: 
If a subdocument has a header and/or footer that is changed, updating the master document (Tools | Update All) does NOT reflect the change to the header and/or footer. Deleting the subdocument and then reinserting it, even after shutting down LibreOffice and restarting, continues to show the old version of the subdocument. 

Steps to reproduce:
1. Create a subdocument containing headers and/or footers; insert into master document.
2. Change (or turn off) the header and/or footer in the subdocument and save it.
3. Update the master document (Tools | Update All).

Current behavior:
The version of the subdocument in the master document continues to show the original header/footer.

Expected behavior:
The master document should show the update header/footer.

Platform (if different from the browser): 
    Xubuntu Linux 12.04; LibreOffice Build ID e29a214

Browser: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0.1
Comment 1 Flemming from Banana hill 2013-01-30 13:12:03 UTC
Same issue with LibreOffice in Fedora 17 (64-bit).
Comment 2 Joel Madero 2013-06-24 17:26:00 UTC
Sorry for the long delay but can you provide more detailed steps:

for instance "insert into master document" (how)

QA doesn't know every detail about LibreOffice and sometimes users use features that we just aren't very familiar with - therefore, expanding on steps and making them explicit (go to file -> new -> document) etc.... helps tremendously to make the progress go smoother.

Marking as NEEDINFO - once steps are provided in greater detail mark as UNCONFIRMED and we will try to confirm quickly. Thanks!
Comment 3 QA Administrators 2014-02-02 02:06:56 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team
Comment 4 QA Administrators 2014-02-26 19:31:25 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO