Bug 826554 - GtkStyle background color regression. Some widget cannot be read.
GtkStyle background color regression. Some widget cannot be read.
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: gtk3 (Show other bugs)
17
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-30 09:51 EDT by Kazuo Moriwaka
Modified: 2012-10-17 01:02 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-10-17 01:02:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 671437 None None None Never

  None (edit)
Description Kazuo Moriwaka 2012-05-30 09:51:52 EDT
Description of problem:

Some widgets in evolution are not readable by too dark background.
This come from gtk3 default theme's regression.

Version-Release number of selected component (if applicable):

F17, gtk3-3.4.3-2.fc17.i686

How reproducible:

always

Steps to Reproduce:

1. start evolution 
2. look an e-mail or browse calendar.
  
Actual results:

e-mail preview widget's background and calendar background(not working hours) are black(#000000) and this cannot readable.

Expected results:

e-mail preview widget's background and calendar background are gray and readable.

Additional info:

These widgets' background color is come from gtk default css's background.
Same trouble is found in arch linux and investigeted in gnome desktop bugzilla.

workaround without build: insert following lines to top of theme's gtk.css 
------------
* {
 background-color: @bg_color;
}
------------
Comment 1 Kazuo Moriwaka 2012-10-17 01:02:10 EDT
this was evolution's problem, and fixed.  I close this case. 
thanks,

Note You need to log in before you can comment on or make changes to this bug.