Bug 118853 - DOCX is not readable as an attribute is included more then once
Summary: DOCX is not readable as an attribute is included more then once
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:docx
Depends on:
Blocks: DOCX-Opening
  Show dependency treegraph
Reported: 2018-07-20 11:03 UTC by Michael Becker
Modified: 2019-05-25 02:57 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Becker 2018-07-20 11:03:58 UTC
After saving a document in DOCX format, I was not able to open the just saved document. lowriter displayed the following error message:

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]: Attribute w:cstheme redefined

I have unziped and searched through word/document.xml and found the following:

<w:rFonts w:eastAsia="Times New Roman" w:cs="Calibri Light" w:cstheme="majorHAnsi" w:ascii="Calibri Light" w:hAnsi="Calibri Light" w:cstheme="majorHAnsi"/>
<w:sz w:val="30"/>
<w:szCs w:val="30"/>
<w:lang w:val="en-US" w:eastAsia="de-DE"/>
<w:t xml:space="preserve">extra-low voltage </w:t>

So the element w:rFonts contains wcsTheme twice with the same value.
Comment 1 Michael Becker 2018-07-20 11:06:34 UTC
PS: Problem arose on Ubuntu 16.04.4 LTS (Xenial Xerus)
Comment 2 Julien Nabet 2018-07-23 15:54:56 UTC
5.1.6 version is EOL.

Could you give a try to a more recent LO version (>= 6.0.5)? You may find recent versions of LO in LO ppa.
Comment 3 Michael Becker 2018-07-23 16:37:06 UTC
The problem ocurred with a document of 17 pages with tables. I simply stored the file every now and then to void data loss. I have no idea how to reproduce it. Thus I am not able to check newer versions.

Perhaps someone has the time to check if there is a chance that the mentioned attribute is inserted twice.

It also would help if the XML file would not be stored as one line, as this would ease to find the relevant line and correct the file by hand. Currently this is a real burden.
Comment 4 Xisco Faulí 2018-07-25 08:12:02 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
(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 5 Michael Becker 2018-07-30 17:51:04 UTC
Sorry - but I am not allowed to publish more then the lines I have included in my first comment.
Comment 6 Xisco Faulí 2018-07-31 09:16:35 UTC
> So the element w:rFonts contains wcsTheme twice with the same value.

Does the problem gets fix if you remove the duplicated attribute?
Comment 7 Michael Becker 2018-07-31 09:55:45 UTC
Comment 8 Xisco Faulí 2018-08-07 15:41:17 UTC
(In reply to Michael Becker from comment #7)
> yes

Hi Michael Becker,
Is there any change you could share with me the document privately sending it to my email?
It would allow me to investigate the issue further...
Comment 9 QA Administrators 2019-03-21 11:12:19 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2019-05-25 02:57:47 UTC
Dear Michael Becker,

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