Bug 247999 - KDE4 color scheme is not consistently applied to SeaMonkey
Summary: KDE4 color scheme is not consistently applied to SeaMonkey
Status: RESOLVED DUPLICATE of bug 234880
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-15 22:59 UTC by Tristan Miller
Modified: 2010-09-16 16:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2010-08-15 22:59:34 UTC 
Version:           unspecified (using KDE 4.5.0) 
OS:                Linux



Reproducible: Sometimes

Steps to Reproduce:
1. Make sure System Settings->Application Appearance->Colors->Options->Apply colors to non-KDE4 applications is enabled
2. Launch SeaMonkey, either from the Application Launcher, from KRunner, or from a shell command line in Konsole

Actual Results:  
3. When launched from Konsole, SeaMonkey is never given the KDE4 colour scheme.  When launched from the Application Launcher or from KRunner, the first few times it does not have the KDE4 colour scheme, but subsequently it does.

Expected Results:  
3. When "Apply colors to non-KDE4 applications" is checked, SeaMonkey (a GTK+ application) should always use the KDE4 colour scheme.
Comment 1 Christoph Feck 2010-08-16 01:57:21 UTC 

*** This bug has been marked as a duplicate of bug 234880 ***
Comment 2 Tristan Miller 2010-08-16 09:23:47 UTC 
Christoph, are you sure this is the same bug as Bug 234880?  That bug talks about one particular colour not being applied to GTK applications.  In my report, *none* of the colours are being applied when the application is launched a particular way.
Comment 3 Tristan Miller 2010-09-16 16:41:12 UTC 
Now the colour scheme is never applied for me no matter how I launch SeaMonkey.  Other GTK+ applications behave likewise.  I guess it's the same bug after all... or at least it is now. :)