Bug 167729 - FORMATTING: Header formatting updates only when changing "Same content on left and right pages" box
Summary: FORMATTING: Header formatting updates only when changing "Same content on lef...
Status: RESOLVED DUPLICATE of bug 168196
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
25.2.5.2 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-30 05:57 UTC by Eero Varkemaa
Modified: 2025-08-30 12:40 UTC (History)
0 users

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 Eero Varkemaa 2025-07-30 05:57:47 UTC
Description:
When trying to change formatting of a page header (height, spacing), the "apply" button does nothing. The changes only take effect when I tick (or untick, if it was already ticked) the "Same content on left and right pages" box and press apply again. If I want to change the formatting again, the box has to be unticked (or ticked) before applying for the changes to take effect. 

"Same content on first page" box is also bugged, but I couldn't figure out what it did. It messed up the formatting completely, maybe reverting to earlier formatting where I tested putting huge numbers to the spacing and height fields. 

Steps to Reproduce:
1. Add a header to document.
2. Go to Format -> Page Style -> Header 
3. Change any setting (except "Same content on left and right pages" or "Same content on first page".
4. Click "Apply"

Actual Results:
Nothing happened

Expected Results:
The header formatting should change to match the new settings. 


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 25.2.5.2 (X86_64) / LibreOffice Community
Build ID: 520(Build:2)
CPU threads: 4; OS: Linux 6.15; UI render: default; VCL: kf6 (cairo+wayland)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
25.2.5-1
Calc: threaded
Comment 1 Justin L 2025-08-30 12:40:53 UTC

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