Bug 195677 - Default colours in non-kde apps are different than after applying oxygen colour theme
Summary: Default colours in non-kde apps are different than after applying oxygen colo...
Status: RESOLVED DUPLICATE of bug 268567
Alias: None
Product: systemsettings
Classification: Applications
Component: krdb (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-08 16:02 UTC by Kamil Neczaj
Modified: 2015-05-07 09:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Default settings (224.97 KB, image/png)
2009-06-08 16:03 UTC, Kamil Neczaj
Details
After applying Oxygen colour theme (256.87 KB, image/png)
2009-06-08 16:04 UTC, Kamil Neczaj
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kamil Neczaj 2009-06-08 16:02:43 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Unlisted Binary Package

I've attached two screenshots. The first shows firefox (gtk) and smplayer (qt) apps with default settings. The second after applying oxygen colour scheme (changing 'Current' scheme to 'Oxygen').Take a look on colours pointed by arrows. They differ with default settings and after applying oxygen colour theme. The colour of window background (1) is darker after applying oxygen theme than before. Colour pointed by arrow 2 in smplayer's configuration window with default settings doesn't match oxygen theme at all.

The colour 1 in both cases don't match kde's window background colour, but default brighter is much better than the darker one.
Comment 1 Kamil Neczaj 2009-06-08 16:03:34 UTC
Created attachment 34373 [details]
Default settings
Comment 2 Kamil Neczaj 2009-06-08 16:04:19 UTC
Created attachment 34374 [details]
After applying Oxygen colour theme
Comment 3 disabled account 2011-05-27 00:45:24 UTC
Wow, you're right (thanks, firefox does now blend in nicely for me).
I don't really know who's to blame for this though.
Comment 4 David Edmundson 2015-05-07 09:48:34 UTC

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