Created attachment 50625 [details]
Contract form with text boxes at the top failing to render properly
The boxes at the top of this doc do not render properly when it is opened with LibreOffice.
Save it in MSWord2007 as .doc, or .odt and in both cases successfully open it in LOWriter
I can not directly open it as .docx or the boxes at the top will not display.
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
reproducible in LibO 3.6.0 master on Fedora 64 bit
but this bug is duplicate of another bug, early reported
[Reproducible] with parallel installation of Master "LOdev 3.6.0alpha0+ – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: 35ec153]" (tinderbox: Win-x86@6-fast, pull time 2012-05-02 06:53:41), pls. compare screenshots.
I found lots of Bug reports sounding similar, but I failed to find one to what this one is a DUP.
Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug
Created attachment 61008 [details]
The reported bug is no more in LO 4.1.1 on Windows 7, but now there is a second blank page who should don't even exist (the doc is made up by 5 pages, not 6).
With LO 4.2-master everything is OK, no reported bug and no blank page, all 5 pages correctly shown.
I fail to reproduce this bug. Tested using LibreOffice Version: 18.104.22.168.alpha0+
Build ID: a82ff18269e5b37348d402b7c21c3f200068265c
TinderBox: Win-x86@39, Branch:master, Time: 2014-07-20_02:34:36
All 5 pages show correctly (no 6 as described already in comment 5).
I'll attach a PDF export of this LibreOffice version.
Marking as RESOLVED WORKSFORME due the fact we don't know exactly which commit fixed this issue.