FILESAVE DOCX: Overlapping images on file open
Steps to Reproduce:
1. Open the attached file
2. Save as DOCX
3. File reload
4. Scroll down to page 80 following -> images overlapping images & text
All sorts of quirky behavior when deleting something in the docx etc
images overlapping images & text
Not be so
User Profile Reset: No
but not in 6.2
Created attachment 163472 [details]
Attempt a bibisect on Windows, but stuck at period save reluctant to save
Strange behavior includes not being able to select (misplaced) images
Bibisected the change to the following commit, using repo bibisect-linux-64-6.3. Adding CC: to Justin Luth.
author Justin Luth <firstname.lastname@example.org> 2018-12-11 15:55:26 +0300
committer Miklos Vajna <email@example.com> 2018-12-14 14:08:35 +0100
sw export: restore ww8 FormatBreak() to pre-2014 logic
I'm not reproducing.
Plus, when I get near the bottom like that, I always get an OUString assert in the dev environment.
Can you create a minimal (1 or 2 page) version of the file highlighting just the problem? If not, can you provide a screenshot to identify the specific pictures, since I wouldn't necessary trust a "page number" since the original document is only 75 pages.
(In reply to Justin L from comment #5)
> I'm not reproducing.
> Plus, when I get near the bottom like that, I always get an OUString assert
> in the dev environment.
> Can you create a minimal (1 or 2 page) version of the file highlighting just
> the problem? If not, can you provide a screenshot to identify the specific
> pictures, since I wouldn't necessary trust a "page number" since the
> original document is only 75 pages.
Not seeing the report problem either.. But likely hidden because of massive footers (page 46/74/76).. will create a report for that first :-)
Needinfo per comment #5. Please minimize this beast.
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker