Bug 135091 - FILESAVE DOCX: Overlapping images on file open
Summary: FILESAVE DOCX: Overlapping images on file open
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.0.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: DOCX-Images
  Show dependency treegraph
 
Reported: 2020-07-24 09:54 UTC by Telesto
Modified: 2021-11-26 04:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
Example file (3.03 MB, application/vnd.oasis.opendocument.text)
2020-07-24 09:54 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-07-24 09:54:07 UTC
Description:
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

Actual Results:
images overlapping images & text

Expected Results:
Not be so


Reproducible: Always


User Profile Reset: No



Additional Info:
Found in
7.1

and in
6.3

but not in 6.2
Comment 1 Telesto 2020-07-24 09:54:26 UTC
Created attachment 163472 [details]
Example file
Comment 2 Telesto 2020-07-24 09:55:22 UTC
Attempt a bibisect on Windows, but stuck at period save reluctant to save
Comment 3 Telesto 2020-07-24 09:57:14 UTC
Strange behavior includes not being able to select (misplaced) images
Comment 4 Aron Budea 2020-09-21 00:44:22 UTC
Bibisected the change to the following commit, using repo bibisect-linux-64-6.3. Adding CC: to Justin Luth.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=5f0cfbbe1840428b07c1ba807ca8123df60bd8a0
author		Justin Luth <justin_luth@sil.org>	2018-12-11 15:55:26 +0300
committer	Miklos Vajna <vmiklos@collabora.com>	2018-12-14 14:08:35 +0100

sw export: restore ww8 FormatBreak() to pre-2014 logic
Comment 5 Justin L 2020-09-21 08:38:29 UTC
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.
Comment 6 Telesto 2020-09-21 08:58:21 UTC
(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 :-)
Comment 7 Gabor Kelemen (allotropia) 2021-04-28 06:49:23 UTC
Needinfo per comment #5. Please minimize this beast.
Comment 8 QA Administrators 2021-10-26 04:44:32 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2021-11-26 04:44:15 UTC
Dear Telesto,

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp