GNOME Bugzilla – Bug 330020
Window-selector doesn't follow color of panel (and doesn't support transparency either)
Last modified: 2006-03-11 19:54:19 UTC
Please describe the problem: Add the window-list to the panel and observe a display glitch. The background of the applet is noticebaly different from other objects such as e.g. the clock applet of the menu-applet or the panel itself. Steps to reproduce: 1. Just add the applet to the panel 2. choose/try with diffferent themes, try transparency as well. Actual results: Window-selector applet doesn't match the color of the panel, when using transparency it has a black background. Expected results: Applet should have the very same background as other applets (esp. clock applet since that is usually the one right next to it) Does this happen every time? No, not every time. One theme that works fine is Grand Canyon, themes that don't work include Clearlooks. Other information: Please refer to the screenshots.
Created attachment 58769 [details] screenshot showing clearlooks with panel set to "use system color" This screenshot shows the selector applets and parts of the clock-applet. Notice the different backgrounds.
Created attachment 58770 [details] screenshot with panel set to color with transparency Another screenshot, showing the same thing, but now with the panel's color set to color with transparency. the selector-applet is black, no matter wat amount of transparency you choose. If you set it to "solid color", it still doesn't match the selected color, but shows a similar effect like depicted in the other screenshot.
I'm reluctant to mark it as a dupe (because I'm not a maintainer or anything like that), but take a look at bug #319845 - really, really looks like it's the same, and that it might well be an engine issue. What was the GTK+ theme used when you took the transparency shot?
Yes, one part is the same as bug #319845 - but my main concern here was the broken transparency - but you gave the right hint here as well - it is an engine issue. I mark this one as duplicate of the engine-issue. Since I already know that I don't have the privileges to actually close an issue, feel free to do so. *** This bug has been marked as a duplicate of 325760 ***