Bug 161630 - Disappearing header and footer
Summary: Disappearing header and footer
Status: RESOLVED DUPLICATE of bug 160139
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-18 10:08 UTC by aaroe
Modified: 2024-06-18 10:21 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aaroe 2024-06-18 10:08:00 UTC
Description:
I am using the latest version. I set up files using a template. After opening the newly created file the header and footer appear to be correct but after editing the file the header and footer disappear. I insert the correct information again, but it often happens again before I save the file. After saving the file with header and footer in place, and reopening it, the h & f appear correct but again disappear after adding information or editing.

Steps to Reproduce:
1.set up a template including header and footer with page numbers in header
2.use the template and begin the document 
3.after a couple of pages h & f content disappear although their placement remains

Actual Results:
the place for the h & f remain but are empty

Expected Results:
the file should keep the h & f after saving and reopening the file.


Reproducible: Always


User Profile Reset: No

Additional Info:
formatting
Comment 1 Stéphane Guillou (stragu) 2024-06-18 10:21:49 UTC
Thanks for the report.
This is very likely because of a paste action, and the issue is tracked in bug 160139.
I am marking as duplicate, but please keep an eye out to see if the header disappears because of one of these actions:
- Zotero update of bibliography / fields
- paste from Calc
- paste as RTF
- paste after copying from a shape
- ... or something else.

(and please update to 24.2.4 or above, as part of the issue was resolved.)

Thank you!

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