After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 142875 - wrong color displayed in tabs for lighthouse blue theme.
wrong color displayed in tabs for lighthouse blue theme.
Status: RESOLVED DUPLICATE of bug 106156
Product: gtk-engines
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal trivial
: ---
Assigned To: Thomas Wood
Thomas Wood
Depends on:
Blocks:
 
 
Reported: 2004-05-21 02:24 UTC by Sean Proctor
Modified: 2005-12-14 21:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6

Attachments
partial screenshot demonstrating the bug (3.02 KB, image/png)
2004-05-21 02:27 UTC, Sean Proctor 		Details

Description Sean Proctor 2004-05-21 02:24:59 UTC 
I'm not exactly sure. I've been seeing variations on this bug for some time. I
don't know if this is in all themes or just the lighthouse blue theme.
Basically, it'll paint a widget half in one color, and half in another color. I
think it's cause by only a portion of a widget being exposed, but I'm not
certain on that. I'll include an image demonstrating the problem. I've been
seeing this problem since at least GNOME 2.2 and it still exists in 2.6.
Comment 1 Sean Proctor 2004-05-21 02:27:53 UTC 
Created attachment 27896 [details]
partial screenshot demonstrating the bug
Comment 2 Farzaneh Sarafraz 2005-07-21 12:49:32 UTC 
this bug report doesn't describe the bug well. If you have time and can still
reproduce the bug in a newer gnome version, please read
http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to
this bug.
Comment 3 Calum Benson 2005-08-08 15:13:25 UTC 
Re-assigning to gtk-engines.
Comment 4 Benjamin Berg 2005-08-20 19:10:08 UTC 
I can reproduce this bug reliably with the gnome-volume-control.
Comment 5 Thomas Wood 2005-12-14 21:42:09 UTC 
I think this is a duplicate of bug 106156.

*** This bug has been marked as a duplicate of 106156 ***