Bug 160236

Summary:	Page numbers inserted into the footer disappear when I update references via the zotero plugin
Product:	LibreOffice	Reporter:	Max <MaximilianScherer>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	stephane.guillou
Priority:	medium
Version:	24.2.1.2 release
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description Max 2024-03-17 03:19:40 UTC

Description:
It doesn't matter whether references are refreshed, a new one is inserted or formatted in another way, it always results in all page numbers being deleted from the the footer.

Steps to Reproduce:
1. Open a new document
2. Insert a reference
3. Insert page numbers
4. Add bibliography

Actual Results:
Page numbers are removed

Expected Results:
Page numbers should not be removed


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 24.2.1.2 (X86_64) / LibreOffice Community
Build ID: 420(Build:2)
CPU threads: 32; OS: Linux 6.7; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
24.2.1-4
Calc: threaded

Comment 1 Stéphane Guillou (stragu) 2024-04-03 07:12:07 UTC

Thanks for the report!

I can reproduce that the footer (which contains the page numbers) is removed when:
- inserting a bibliography
- inserting a reference that automatically update the bibliography
- refreshing with the Refresh buttom in the Zotero toolbar

...with Zotero 6.0.35 and:

Version: 24.2.2.1 (X86_64) / LibreOffice Community
Build ID: bf759d854b5ab45b6ef0bfd22e51c6dc4fb8b882
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

Not reproduced in:

Version: 7.6.6.3 (X86_64) / LibreOffice Community
Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: CL threaded

This regression is most likely the same as bug 160139, marking as duplicate.

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