Created attachment 2145 [details]
Screenshot

Screenshot of my desktop

Well, oxygen-gtk has no way to "force itself" as a widget style.
So it means that some "relic" config file still charges it.
Technically this is not an "oxygen-gtk" bug. Some (distribution related) issue with configuration files.

look into $HOME/.gtkrc* to see if it still appears somewhere.

From the first attachment, it seems it is still used by xfce4-session, xfwm4, Thunar, etc (just grep ApplicationName::initialize to see which applications initialize it)

Also, on the second attachment (screenshot), it is not clear to me *what* actually uses oxygen-gtk. (it looks rather like either Adwaita or clearlook widget style). Can you comment ? 

Cheers,

Hugo

(In reply to comment #2)
> Well, oxygen-gtk has no way to "force itself" as a widget style.
> So it means that some "relic" config file still charges it.
> Technically this is not an "oxygen-gtk" bug. Some (distribution related) issue
> with configuration files.
> 
> look into $HOME/.gtkrc* to see if it still appears somewhere.
> 

I've checked all files in $HOME many times and finally found it. Our adwaita theme pkgs comes with system wide gtkrc [1] file for GTK+2.0 and settings.ini [2] for GTK+3.0 that forces use of oxygen theme.

I've not had oxygen installed never before so I've not hit this problem until now. I guess if oxygen isn't installed, some other/fallback theme is used. This would also explain why this "problem" occurs only when oxygen-gtk is installed. 

IMHO it's a bit weird that adwaita theme forces to use another theme. 

[1] http://svnweb.mageia.org/packages/cauldron/gnome-themes-standard/current/SOURCES/gtkrc?view=markup
[2] http://svnweb.mageia.org/packages/cauldron/gnome-themes-standard/current/SOURCES/settings.ini?&view=markup

There's still something in somewhere as I removed both of those files and still oxygen get started when Xfce starts. :( I've removed all per user config files and system wide oxygen settings.

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Closing as old.

Status: NEW => RESOLVED
Resolution: (none) => OLD

Well, there is still same thing happening in MATE. Basically, almost everything is set in order with current theme but oxygen-gtk border colors overrides current themes border color settings. 

I' m told that it is only seen Mageia, by MATE and Fedora devs. And we use both oxygen-gtk and /etc/gtk-2.0/gtkrc. Uninstalling oxygen-gtk theme fixes this issue, but removing /etc/gtk-2.0/gtkrc is not.

Status: RESOLVED => REOPENED
CC: (none) => tarakbumba
Hardware: i586 => All
Resolution: OLD => (none)
Severity: normal => major

New info about this issue, if i change "gtk-theme-name" to something else, say gtk-theme-name = "xl_monochrome" than window borders are displayed with correct colour. Weird...

@Atilla
Although what you report in comment 7 and 8 is likely a different issue/bug from the one originally reported, the information you provided is very usefull. Most likely it means that oxygen-gtk does not respect the color set by a custom gtkrc file (that defines the decoration colors) and forces the ones it reads from the (KDE) color palette (or its default palette, in absence of a KDE one). 

I'll investigate on that. 
Would you care file a bug upstream directly ? (https://bugs.kde.org, product oxygen, component gtk2 engine) ? That makes my life easier for bookkeeping (and the bug should not be specific to mageia anyway)

Regards,

Hugo

PS: do you know if mate decorations use gtk2 or gtk3 ?

(In reply to Hugo Pereira Da Costa from comment #10)
Mate uses gtk2. Here is the bug report you asked for:

https://bugs.kde.org/show_bug.cgi?id=330768

Hope, this issue will fixed.

Is this still current?

CC: (none) => nic

(In reply to Nic Baxter from comment #12)
> Is this still current?

No reply and we no longer use Oxygen by default, closing as OLD

Status: REOPENED => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD