Description of problem: Some panel applets become unusable when using a fully-opaque solid color panel, and some will not recover until the panel color is reset to "None." Version-Release number of selected component (if applicable): gnome-applets-2.6.0-8 How reproducible: Always. Steps to Reproduce: 1. Open "Panel Properties." 2. In the "Background" tab, choose "Solid color." 3. Move the "Style" slider to "Transparent." The panel should now be transparent. This is shown in screen shots named '*-1'. 4. Move the slider to "Opaque." As shown in the screenshots named '*-2', some of the applets become unusable. 5. Move the slider back to "Transparent." As shown in the screenshots named '*-3', some of the applets recover and some don't. Actual results: See "Steps to Reproduce" Expected results: Panel applets should either gracefully obey color and opacity settings, or else completely ignore them. Background color and text color should not be allowed to be the same (or even too close, ideally). Additional info: Missing from the "Utility" screenshots are "InputMethod Switcher" and "System Monitor" which keep making my panel crash... more on that later.
Created attachment 101766 [details] screenshots
Yeah, this is a known issue and I think most applets with the problem have bugs reported against them (we need a bug for each applet). I'm going to close this UPSTREAM since we'll probably never get around to fixing each applet. It would be good, though, if you could ensure each applet with the problem has a bug logged against it in bugzilla.gnome.org. Thanks ...
I meant to close this as UPSTREAM myself. I filed this bug on gnome-panel and gnome-applets, but the one on -applets was closed as a duplicate. I assume if I file 10 more, they will as well :) Should I do it anyway? http://bugzilla.gnome.org/show_bug.cgi?id=147447
This one is still open, though: http://bugzilla.gnome.org/show_bug.cgi?id=147447 but I'll close that one out as soon as I get a chance to catch up with my upstream bug mail :-) For each applet which you know has the problem, I'd first check to see if the bug has already been logged and if not log it.