Bug 86362 - Page number appeared twice in this .docx document
Summary: Page number appeared twice in this .docx document
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: target:4.4.0
Keywords: regression
Depends on:
Blocks:
 
Reported: 2014-11-17 02:50 UTC by Kevin Suo
Modified: 2014-11-19 03:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
test .docx file (25.26 KB, application/vnd.openxmlformats-officedocument.wordprocessingml)
2014-11-17 02:50 UTC, Kevin Suo 		Details
screenshot showing the issue (290.25 KB, image/png)
2014-11-17 02:57 UTC, Kevin Suo 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Suo 2014-11-17 02:50:20 UTC 
Created attachment 109579 [details]
test .docx file

Page number for the attached .docx document appears twice on document page 2 and 3.

Steps to reproduce:
1. Open the attached .docx file
2. Observe that the page numbers are showing twice on the 2nd and 3rd page.

The page numebrs should show only once.

Broken in:
Version: 4.3.4.1
Build ID: bc356b2f991740509f321d70e4512a6a54c5f243

OS: Win 7 X64

Works OK with:
Version: 4.4.0.0.alpha2
Build ID: 24f0a5815f581dd9a7f09d30213a379edee6e9ac
Comment 1 Kevin Suo 2014-11-17 02:57:04 UTC 
Created attachment 109580 [details]
screenshot showing the issue
Comment 2 tommy27 2014-11-18 21:42:47 UTC 
also broken in 4.3.3.2 under Win7x64
works fine in 4.2.6.2

however since it's working in 4.4.0.0 alpha2 (which I confirm with a recent daily build) we have to set status as RESOLVED WORKSFORME

let's hope that the fix could be backported to future 4.3.x releases
Comment 3 Kevin Suo 2014-11-19 02:21:16 UTC 
Hi tommy,

Version 4.3.4.1 is the current stable version. There are still 3+ minor releases for 4.3 branch.

I think we should keep this bug as NEW until it's really fixed in 4.3 branch, because:
* Maybe someone made a commit to master and fixed this issue, but forgot to backport it to 4.3.
* Or, this bug was caused by a commit in 4.3 branch only (did not affect master branch).
Comment 4 Kevin Suo 2014-11-19 02:21:47 UTC 
Set to NEW according to comment 2 and comment 3.
Comment 5 tommy27 2014-11-19 03:28:17 UTC 
No Kevin,
this is not how it works... you should know that once a bug is fixed in the master branch it has to be labeled as fixed even if issue persists in the stable branch.

so I'm reverting status to WFM.

4.4.0 will be out in february 2015.
if you are interested in a 4.3.x backport you can try doing a reverse bibisect to identify which committ fixed this in the 4.4.x branch, then contact the developer and ask if he can push the fix in the 4.3.x branch as well