Bug 695456 - Very low contrast on calendar panel widget
Summary: Very low contrast on calendar panel widget
Keywords:
Status: CLOSED DUPLICATE of bug 693565
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Bill Nottingham
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-11 19:24 UTC by Havard
Modified: 2014-03-17 03:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-11 19:42:41 UTC
Type: ---

Attachments (Terms of Use)
Top panel, low contrast icons (4.95 KB, image/png)
2011-04-11 19:24 UTC, Havard 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Havard 2011-04-11 19:24:22 UTC 
Created attachment 491321 [details]
Top panel, low contrast icons

Description of problem:

The Clock appelet (/usr/libexec/clock-applet) in the panel is almost black, on black background. The contrast is so low that it is almost invisible. Testing on an older CRT monitor, it is not visible at all. Please see the attached
screenshot.

Please note, this is on the Fedora 15 Alpha Live CD, x86_64.

Also note, it seems like the live CD did not boot into the new Shell WM, but
rather use the older looking fallback WM.

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

Clock 2.91.6


How reproducible:

Observe the icon in the panel after boot.


Actual results:

The text is invisible. Although it gets a grey background when the mouse hovers.

Expected results:

In Fedora 14, the icon is clearly visible, with black on light gray background.



Additional info:

Linux 2.6.38-0.rc5.git1.1.fc15.x86_64

Asus M3A78 PRO MB, with on board ATI Radeon HD 3200 GPU.
http://www.asus.com/Motherboards/AMD_AM2Plus/M3A78_PRO/

Monitors: Dell 2709w, and old 17'' CRT.
Comment 1 Havard 2011-04-11 19:42:41 UTC 

*** This bug has been marked as a duplicate of bug 693565 ***
Note You need to log in before you can comment on or make changes to this bug.