As per bug I filed with my distro (https://bugs.archlinux.org/task/33669) the latest oxygen-gtk2 update is buggy: 1) Oxygen-gtk2 is no longer using my color scheme in several places (XFCE panel, pinentry dialog, etc.) 2) Leafpad fails with a segfault. Reproducible: Always Steps to Reproduce: 1. Install latest oxygen-gtk2 package. 2. Launch my desktop (XFCE), which is set to use the oxygen-gtk style. 3. Launch leafpad. Actual Results: 1. XFCE panel shows in (default) silver color. 2. Pinentry dialog (i.e., launched to enable passphrase entry when I SSH into a machine) shows in default silver color. 3. Leafpad issues a segfault when I try to invoke it. Expected Results: 1. All of the above should display in the dark blue that I use in my KDE color configuration (See http://www.darose.net/Dark-Blue-Grey-Dave9.kcsrc), and not the default silver color. 2. Leafpad should be able to launch successfully. Downgrading back to 1.3.1 makes the all of these problems go away.
Thanks for reporting, This is likely the same issue as for bug 272570. I 'think' I know the reason for this, though the "buggy" change was introduce to fix some initialization issues under gnome 3. I'll revert and find a better fix for gnome 3. Will likely have a new bugfix release (like 1.3.2-1) by the end of the week. In the meanwhile please - send this link to your distro bug - recommand your distro to roll-back to 1.3.1 Sorry for the trouble (and damn DEs, I must say)
Heh, I was wondering why I have some apps using half-correct and half-default color scheme :) ( http://i0.simplest-image-hosting.net/picture/screenshot-02062013-113913-pm.png ) I thought it was related to recent glibc upgrade, but now it appears that it's this bug.
@Ruslan nice that you can reproduce ! it means you'll be able to test my patches :) here with KDE, all seems to be working, but many I did not test enough applications.
@Ruslan the details: in 1.3.1, oxygen's initialisation happens in theme_init. This is causing issues with gnome 3, because when theme_init is called, for some reason, gdkscreen is not yet defined, nor gtksettings (which we obviously need). You end up with zillions of warnings and initialization incomplete. So I moved it to ::instance_init. This fixes all the issues I see with gnome 3, but obviously fails elsewhere: create recursive calls to instance_init for some (but not all applications), and some incomplete initialisations ... So. Need to find a way to "try" to make the initialization twice, at both places, and keep the first one that works. Possibly by testing the validity of gdkscreen. Should work :) But needs more testing than my too hasty release. (I guess I don't use enough gtk)
PS: what's the application in your screenshot ?
(In reply to comment #5) > PS: what's the application in your screenshot ? It's one of my first GTK apps - inspired by windows task manager; incomplete&ugly inside, but still usable for logging CPU&memory usage. I can send it to you if you want to test your patches.
BTW, it seems we've missed actual 1.3.1 git tag - there's only 1.3.0 and 1.3.2.
*** Bug 272570 has been marked as a duplicate of this bug. ***
Created attachment 76974 [details] proposed patch Hi, patch attached should fix the issues. It basically rollback the guilty change, add some more tests in settings initialisation and attempt at redoing the initialization in instance_init if it failed in theme_init. So that things should be back to normal, and things are more or less working in gnome3 (no warning, and full initialization there too). More or less: some applications (e.g. ardour) are still crashing, but only for gnome 3 (because the first initialization fails). in the end I suspect the latter behavior is actually an upstream bug ... Will investigate some more. I'd be glad if reporters could check the patch, before pushing and creating a new release. I can provide instructions on how to build code from source and apply the patch if needed. Hugo
Created attachment 76975 [details] updated patch. Previous one was incomplete Sorry for the noise; previous patch was incomplete, please ignore. This one is complete ... Hugo
The patch fixes my problem starting ardour, thanks.
Looks fixed. Colors display correctly in latest version, and leafpad doesn't segfault. Thanks for the quick fix, Hugo!
Fixes my problems too. Also see this: http://simplest-image-hosting.net/png-0-screenshot-02072013-070231-pm . This is with OXYGEN_APPLICATION_NAME_OVERRIDE=asdfasf. Notice different colors in toolbar. The patch also fixes it.
ok. Thanks for the testing. Still, I'm not happy with ardour crashing under gnome 3. And possibly all the 'other' issues you report there will also occur ... I'll push the change to git though.
*** Bug 315163 has been marked as a duplicate of this bug. ***
The recent bugfix release 1.3.2.1 doesn't fix it for me in Firefox.See dupe bug 315163.
(In reply to comment #16) > The recent bugfix release 1.3.2.1 doesn't fix it for me in Firefox.See dupe > bug 315163. Strange. Could you provide a screenshot? I remember to have seen something similar before, but now it *is* fixed for me, maybe we are talking about different things.
Created attachment 77357 [details] Screenshot of Firefox with grey textfields