Bug 111622 - FILEOPEN DOCX - Writer gets wrong color scheme, if color is set to 'Automatic'
Summary: FILEOPEN DOCX - Writer gets wrong color scheme, if color is set to 'Automatic'
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
Keywords: filter:docx
Depends on:
Blocks: OOXML-Chart
  Show dependency treegraph
Reported: 2017-08-10 04:17 UTC by Mike
Modified: 2022-11-27 03:37 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:

Testcase (25.84 KB, application/zip)
2017-08-10 04:18 UTC, Mike
Screenshot of Word 2007 (73.75 KB, image/png)
2017-08-10 04:19 UTC, Mike
Comparaison (134.83 KB, image/png)
2017-08-10 06:24 UTC, halima
Minimum test case (10.57 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2017-11-22 20:25 UTC, Mike
Manually "fixed" Minimum test case (10.64 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2017-11-22 20:26 UTC, Mike
Screenshots and description (240.54 KB, application/pdf)
2017-11-22 20:35 UTC, Mike

Note You need to log in before you can comment on or make changes to this bug.
Description Mike 2017-08-10 04:17:41 UTC
When I open the file with Writer, it shows the chart in greyscales. But "Datenreihe 3" is green, "Datenreihe 2" is red and "Datenreihe 1" is blue. I created this document with Word 2007.

Steps to Reproduce:
1. Open file.

Actual Results:  
Writer renders a chart with different grey colors

Expected Results:
Writer renders a chart with red, green and blue.

Reproducible: Always

User Profile Reset: No

Additional Info:

User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0
Comment 1 Mike 2017-08-10 04:18:44 UTC
Created attachment 135391 [details]
Comment 2 Mike 2017-08-10 04:19:17 UTC
Created attachment 135392 [details]
Screenshot of Word 2007
Comment 3 halima 2017-08-10 06:24:09 UTC
Created attachment 135394 [details]

Same document opened with MSO Word is in colour and with LO writer it's in black and white as you can see in the attached image 

LO Version: (x64)
Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c
Threads CPU : 4; OS : Windows 6.19; UI Render : par défaut; 
Locale : en-GB (fr_FR); Calc: group

MSO WORD version 2016
Windows 10
Comment 4 Jacques Guilleron 2017-08-10 07:24:17 UTC

Reproduced too with
LO (x64) Build ID: 92c2794a7c181ba4c1c5053618179937228ed1fb
Threads CPU : 2; OS : Windows 6.1; UI Render : par défaut; 
Locale : fr-FR (fr_FR); Calc: single
LO Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale : fr_FR 
under Windows 7
Comment 5 Mike 2017-11-22 20:25:49 UTC
Created attachment 137921 [details]
Minimum test case
Comment 6 Mike 2017-11-22 20:26:15 UTC
Created attachment 137922 [details]
Manually "fixed" Minimum test case
Comment 7 Mike 2017-11-22 20:35:11 UTC
I created a minimum test case for this issue, that I attached now („Minimum test case.docx“). To create this, I took the original file „Greyscales instead of colors.docx“ and cut it down.

Issue: LO renders the rectangle of „Minimum test case.docx“ in grey scales (instead of blue). Writer gets the wrong color scheme.

Then did I changed the color of the rectangle from "Automatic" to blue. I saved this as „Minimum Text case fixed.docx“. This does the Job for Writer.
In the fixed test case, word\charts\chart1.xml got the more 
lines (line 40 to 42):
<a:schemeClr val="accent1"/>

This issue is there since LO 4.2. From release 3.3 to 4.0 only a blank page appeared (with both files!)

I'm not a coder, but it seems to be about this:


using DocumentFormat.OpenXml.Drawing;
using DocumentFormat.OpenXml;
namespace GeneratedCode
    public class GeneratedClass
        // Creates an SchemeColor instance and adds its children.
        public SchemeColor GenerateSchemeColor()
            SchemeColor schemeColor1 = new SchemeColor(){ Val = 
SchemeColorValues.Accent1 };
            return schemeColor1;

I also attached a PDF with screenshots to this report.


Comment 8 Mike 2017-11-22 20:35:37 UTC
Created attachment 137923 [details]
Screenshots and description
Comment 9 Mike 2017-11-22 20:39:37 UTC
Forgot my configuration:

Version: (x64)
Build ID: a5af0fd9f27af42cf2e8571f659cdad6e606215b
CPU threads: 4; OS: Windows 10.0; UI render: default; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2017-11-07_00:30:02
Locale: de-DE (de_DE); Calc: CL
Comment 10 Buovjaga 2018-03-14 14:32:43 UTC
Still repro.

3.3 shows blank...

Arch Linux 64-bit
Build ID: a7bb853b348cc5ebe4ccdb07d1ee0fc38de21e7a
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on March 14th 2018

Arch Linux 64-bit
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-
Comment 11 QA Administrators 2019-03-15 03:55:34 UTC Comment hidden (obsolete, spam)
Comment 12 Karl 2020-11-16 16:47:18 UTC
This bug is still present in

Version: (x64)
Build ID: d7547858d014d4cf69878db179d326fc3483e082
CPU threads: 12; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: de-AT (de_AT); UI: en-GB
Calc: threaded
Comment 13 QA Administrators 2022-11-27 03:37:47 UTC
Dear Mike,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team