https://bugs.documentfoundation.org/show_bug.cgi?id=147892

            Bug ID: 147892
           Summary: Corrupt DOCX document after saving (track changes
                    involved)
           Product: LibreOffice
           Version: 7.2.5.2 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 178770
  --> https://bugs.documentfoundation.org/attachment.cgi?id=178770&action=edit
diff -u output on document.xml from correct to corrupt DOCX

Two days ago I saved a document containing many tracked changes, including a
new table. When I tried to reopen it, LibreOffice complained that it was
corrupt, and was unable to fix it:

> An error occurred during opening the file. This may be caused by incorrect 
> file contents. The error details are:
> SAXException: [word/document.xml line 2]: Opening and ending tag mismatch: 
> rPr line 2 and ins
> /buildir/build/BUILD/libreoffice-7.2.5.2/sax/source/fastparser/fastparser.cxx:619
> Proceeding with import may cause data loss or corruption, and application may 
> become unstable or crash.
> Do you want to ignore the error and attempt to continue loading the file?

If I choose "Yes" then the file opens, but contents are truncated in the middle
the table I added (with tracked changes) just before corruption happened.

Of course I don't know how to reproduce the bug, but I had a backup of the
previous version of the file, and the diff between the XML code of that
document (which is not corrupt) and the new corrupt one is very limited (apart
from trivial one-line changes), so maybe it can be useful? I'm attaching it. I
can send you both the correct and the corrupt document privately if you're
interested.


Version: 7.2.5.2.0+
Build ID: 20(Build:2)
CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: gtk3
Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to