Bug 150423 - Duplicated themeColor and themeShade in docx roundtrip
Summary: Duplicated themeColor and themeShade in docx roundtrip
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.4.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-15 13:00 UTC by mj.wilson.uk
Modified: 2023-09-02 03:06 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
docx with theme color set (1007.91 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-09-11 07:20 UTC, Alexander
Details
docx with color theme in ms word (1007.91 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-09-11 07:25 UTC, Alexander
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mj.wilson.uk 2022-08-15 13:00:28 UTC
1. Open a docx file (A) saved by MS Word (must have theme colors set)
2. Make no changes
3. Save as docx file (B)
4. Reopen B

Error:
SAXException [word/document.xml line 20]: Attribute w:themeShade redefined

From manual inspection of the XML, the <w:color> elements have a duplicated w:themeShade and w:themeColor attributes.

This does not seem to be possible (from my experience) when creating the document in LibreOffice.  It has to be a document from MS Word that has a color theme set.

I have an example, but it contains proprietary / confidential information.  I can dig out a copy of MS Word and try to create a minimal document if it is useful.

This appears to be a regression of 123705.

$ libreoffice --version
LibreOffice 7.3.4.2 30(Build:2)

$ head -7 /etc/os-release 
NAME="Fedora Linux"
VERSION="36 (Thirty Six)"
ID=fedora
VERSION_ID=36
VERSION_CODENAME=""
PLATFORM_ID="platform:f36"
PRETTY_NAME="Fedora Linux 36 (Thirty Six)"

$ rpm -q libreoffice-writer 
libreoffice-writer-7.3.4.2-4.fc36.x86_64
Comment 1 Xisco Faulí 2022-08-15 14:20:27 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
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 mj.wilson.uk 2022-08-19 14:12:50 UTC
I'm having trouble producing a minimal example that reproduces this issue.

From manual inspection of the XML, the duplicate is in a rPrChange element.  The document does contain a lot of track changes annotations.

However, I cannot reproduce it either with starting from a blank document, or by deleting everything but the offending section.

My next approach will be to replace all characters in the original with "X" and see what happens.

Thanks for your patience.

If there's another way I can debug this (e.g. use libreoffice at the command line with some extra logging options to simulate load/save), or some code I can inspect, please let me know.
Comment 3 QA Administrators 2022-08-20 03:44:54 UTC
[Automated Action] NeedInfo-To-Unconfirmed
Comment 4 Alexander 2022-09-11 07:20:58 UTC
Created attachment 182372 [details]
docx with theme color set
Comment 5 Alexander 2022-09-11 07:25:39 UTC
Created attachment 182373 [details]
docx with color theme in ms word

Not Reproduced

Steps Followed:
1. Open a docx file (A) saved by MS Word (must have theme colors set)
2. Make no changes
3. Save as docx file (B)
4. Reopen B

I did not get any issues while opening in libreoffice writer

Test Environment:
OS: Linux Mint 20.3 Cinnamon
Processor: Intel© Core™ i7-7500U CPU @ 2.70GHz × 2
Software Version: LibreOfficeDev-7.4.0.0.alpha0_2022-01-23-x86_64.AppImage
Comment 6 Buovjaga 2023-02-02 12:09:41 UTC
Do you still repro with 7.4 or 7.5?

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 7 QA Administrators 2023-08-02 03:13:49 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2023-09-02 03:06:04 UTC
Dear mj.wilson.uk,

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