Bug 691288 - [gnome-panel-3] unfocused clock shown in black on black
Summary: [gnome-panel-3] unfocused clock shown in black on black
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-28 04:50 UTC by Jens Petersen
Modified: 2011-09-17 21:45 UTC (History)
3 users (show)

Fixed In Version: gnome-panel-2.91.92-1.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-08 00:11:00 UTC
Type: ---


Attachments (Terms of Use)

Description Jens Petersen 2011-03-28 04:50:44 UTC
Description of problem:
Gnome-panel clock seems to be rendered in dark grey text
on black background when it is not focused.
This makes it a bit hard to see. ;) :)
(In fact I thought it was black on black but staring
at it I see it is actually dark grey, but almost invisible.)

Version-Release number of selected component (if applicable):
gnome-panel-2.91.x

How reproducible:
every time

Steps to Reproduce:
1. login to fallback gnome
2. look at clock
3. move mouse to clock
  
Actual results:
2. can't see time (without staring at clock)
3. grey on white highlighting

Expected results:
2. white or light grey on black

Additional info:
This has been happening for weeks now.
So I thought time to report it...

Comment 1 Jens Petersen 2011-03-29 01:56:21 UTC
Thanks seems fixed in gnome-panel-2.91.92-1.fc15.

Comment 2 Jens Petersen 2011-04-04 10:24:45 UTC
I thought this was fixed but I see it again in fallback mode (kvm)
with Fedora-15-Nightly-20110403.17-i686-Live-desktop.iso.

Comment 3 Matthias Clasen 2011-04-08 00:11:00 UTC
Should be fixed in 3.0.0

Comment 4 cblaauw 2011-09-17 21:45:58 UTC
Seems to be back right now (gnome-panel-3.1.91-3.i686)

In fallback-mode the clock is almost invisible right now


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