Bug 113731

Summary: GTK+ programs - incorrect look on Kicker
Product: [openSUSE] SUSE Linux 10.1 Reporter: Alex Radu <exigentsky>
Component: KDEAssignee: Lubos Lunak <llunak>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: unspecified   
Target Milestone: ---   
Hardware: i686   
OS: SUSE Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Alex Radu 2005-08-29 06:40:19 UTC 
If I minimize a program like Gaim to the Kicker's tray, its lighter background 
stands out and makes the whole desktop seem inconsistent.  
 
However, this can be fixed by disabling the background picture for the kicker. 
If this is done, KDE and GTK+ programs look the same in the system tray and 
there are no consistency problems. (it's also faster)
Comment 1 Stephan Kulow 2005-09-07 08:08:30 UTC 
Lubos, please find out what's causing this and reassign if needed
Comment 2 Stephan Binner 2005-11-23 13:25:36 UTC 
> this can be fixed by disabling the background picture for the kicker

I doubt that, isn't it rather that the background color of the default scheme has the same color as the "light background"?

Anyway, known upstream as http://bugs.kde.org/show_bug.cgi?id=116891
Comment 3 Stephan Kulow 2008-06-25 09:32:54 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 4 Stephan Kulow 2008-06-25 09:34:19 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:40:48 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:52:30 UTC 
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(