Bug 112635 - DOCX is broken after editing with LO. File format error found at SAXParseException
Summary: DOCX is broken after editing with LO. File format error found at SAXParseExc...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: DOCX-SAXParse
  Show dependency treegraph
Reported: 2017-09-25 07:23 UTC by Khalil
Modified: 2018-07-03 14:19 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

DOCX broken file (134.88 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2017-09-25 07:23 UTC, Khalil
DOCX original file (16.08 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2017-09-28 11:48 UTC, Khalil

Note You need to log in before you can comment on or make changes to this bug.
Description Khalil 2017-09-25 07:23:02 UTC
Created attachment 136520 [details]
DOCX broken file

After edeting DOCX file attached with LO then save it and open it again file is broken with error: 
File format error found at 
SAXParseException: '[word/document.xml line 2]: Attribute w:hAnsiTheme redefined
', Stream 'word/document.xml', Line 2, Column 192488(row,col).
Comment 1 Xisco Faulí 2017-09-25 08:03:19 UTC
Hello Khalil,
Thanks for reporting this issue.
The attached file gives the error at import time, thus it seems it's the file created after a roundtrip. Could you please attach the original file?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 2 Khalil 2017-09-28 11:48:53 UTC
Created attachment 136581 [details]
DOCX original file
Comment 3 Khalil 2017-09-28 11:53:23 UTC
Hi  Xisco Faulí ,

Find attached original file after I remove sensitive data. Note: Track changes is active in the file by MSOffice word originally and I notice that editing this file in LO  while track changes is active cause the error, however after I deactivate track changes error didn't show. I don't know if they are related or not.

Comment 4 Xisco Faulí 2017-09-28 13:12:11 UTC
I can't reproduce it in

Build ID: 8d2a287da3abb0576512406227d0a3acd602123e
CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Comment 5 QA Administrators 2018-05-30 16:39:24 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2018-07-03 14:19:40 UTC
Dear Bug Submitter,

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