Bug 107123 - application colors automatic white is mapped to black
Summary: application colors automatic white is mapped to black
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.2.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-12 15:52 UTC by fitbit0901
Modified: 2017-04-17 13:08 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
color white is mapped to black (76.14 KB, image/jpeg)
2017-04-12 15:52 UTC, fitbit0901
Details

Note You need to log in before you can comment on or make changes to this bug.
Description fitbit0901 2017-04-12 15:52:23 UTC
Created attachment 132521 [details]
color white is mapped to black

When starting swriter, scalc, and other applications, the default background color is black.
In examining the application colors, the color white is mapped to black. Please see the attachment.
The user profile has been removed, and the application restarted with the same results.
The user profile has been removed, and a known good profile copied in its place, again with the same results.
No hardware acceleration has been specified.
The GL and GL4 libraries are not chosen.
Comment 1 Xisco Faulí 2017-04-12 20:38:20 UTC
Which OS and theme are you using? Does changing the OS' theme fix the problem?
Comment 2 fitbit0901 2017-04-12 21:16:16 UTC
(In reply to Xisco Faulí from comment #1)
> Which OS and theme are you using? Does changing the OS' theme fix the
> problem?

OS: RHEL 6.8, 
Display manager 1 is GNOME, 
Display manager 2 is Fluxbox.
Changing the desktop theme and/or display manager does not change the behavior.
Comment 3 fitbit0901 2017-04-12 21:20:42 UTC
Also, changing the LibreOffice theme does not help either.
Comment 4 fitbit0901 2017-04-13 12:16:36 UTC
Installed LibreOffice 5.3.2 using installer provided. Still same results.
Comment 5 fitbit0901 2017-04-17 13:08:44 UTC
This was resolved by adding X privileges that had been inadvertently removed.