Bug 150191 - document save corruption
Summary: document save corruption
Status: RESOLVED DUPLICATE of bug 149996
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: DOCX-SAXParse
  Show dependency treegraph
Reported: 2022-07-29 05:56 UTC by Elmar
Modified: 2022-09-23 09:01 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

v01G latest document (406.13 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-07-29 06:09 UTC, Elmar
v01F previous save (345.25 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-07-29 06:10 UTC, Elmar
docx result of save broken (405.93 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-07-29 06:11 UTC, Elmar
odt result of save ok (477.75 KB, application/vnd.oasis.opendocument.text)
2022-07-29 06:12 UTC, Elmar
error message (30.98 KB, image/png)
2022-07-29 06:14 UTC, Elmar
LO v6 save (420.91 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-07-29 06:20 UTC, Elmar

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar 2022-07-29 05:56:03 UTC
When I compare two MSWord format documents and save the result to MSW, the result is corrupt.

Steps to Reproduce:
1.open MSW document v01G
2.open MSW document v01F
save v01G in MSW format

Actual Results:
Open v01G.docx
get error message
most of document is no longer there

Expected Results:
Should work as expected.

Reproducible: Always

User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: en-GB
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes

Version: / LibreOffice Community
Build ID: 43e5fcfbbadd18fccee5a6f42ddd533e40151bcf
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Calc: threaded

If i save the document as ODT it is fine (or so it seems)
Comment 1 Elmar 2022-07-29 06:09:41 UTC
Created attachment 181481 [details]
v01G latest document
Comment 2 Elmar 2022-07-29 06:10:28 UTC
Created attachment 181482 [details]
v01F previous save
Comment 3 Elmar 2022-07-29 06:11:17 UTC
Created attachment 181483 [details]
docx result of save broken
Comment 4 Elmar 2022-07-29 06:12:04 UTC
Created attachment 181484 [details]
odt result of save ok
Comment 5 Elmar 2022-07-29 06:14:14 UTC
Created attachment 181485 [details]
error message

when attempting to open the corrupt file
Comment 6 Elmar 2022-07-29 06:20:55 UTC
Created attachment 181486 [details]
LO v6 save

I then did the same thing with 
Build ID: 1:6.4.7-0ubuntu0.20.04.4
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
Calc: threaded

saved fine, also no problem opening in MSO
Microsoft® Word for Microsoft 365 MSO (Version 2206 Build 16.0.15330.20260) 64-bit

appears to be a regression
Comment 7 Mike Kaganski 2022-07-29 06:41:58 UTC
Repro using Version: (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL

OK using Version: (x64) / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL

For reproduction, no need to download "v01f"; only download attachment 181481 [details], open, save (as DOCX), and reload.
Comment 8 Mike Kaganski 2022-07-29 07:01:58 UTC
Started after commit 7246e57216bb20c15af0ecf6a0183f5ffa81e780
  Author Miklos Vajna <vmiklos@collabora.com>
  Date Mon Sep 20 19:56:37 2021 +0200
    tdf#143591 DOCX import: handle anchored objects as at-char

but it's not a regression *from that commit*, rather, it just made this document affected by bug 149996.

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