https://bugs.kde.org/show_bug.cgi?id=364693
Bug ID: 364693
Summary: When upgrading from Qt5.4 to Qt5.6, the color and
theme handling ignores local settings
Product: Oxygen
Version: 1.4.5
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: gtk2-engine
Assignee: hugo.pereira.da.co...@gmail.com
Reporter: h...@urpla.net
CC: b7.10110...@gmail.com, w...@adishatz.org
First of all: I LOVE OXYGEN-GTK! Thank you very much.
I'm in loving relationship to your project for a long time (even before I was
able to spell oxygen-gtk ;) Coming a long way up, when started with KDE 1.0,
I'm using a special color theme for most of the time, because I don't like all
those cold colored DEs. Needless to say, that I'm very sensitive about changes
in this area. Especially, when defaults come into play..
Using openSUSE 13.2/x86_64 with KDE 4.14 nowadays (for one reason, because
Plasma5 adds another color settings layer on top, due to Qt5). With Qt5.4, that
comes with openSUSE, all is well, Qt5 inherits the KDE4 color settings just
fine, and oxygen-gtk spreads that to the essential Gtk based apps as well
(Firefox, Gimp, LO).
Now I started to prepare for a Qt5.6 based project here:
https://build.opensuse.org/project/monitor/home:frispete:PyQt5
That's a Qt 5.6.1 build, that should work fine as a Qt 5.4.2 replacement.
Unfortunately, immediately after upgrading the packages, Gtk changed its
appearance to oxygens default color map including the background gradient, that
I've disabled. (Firefox menus turned gray).
Some further investigation revealed, that I could either choose Adwaita as GTK2
theme and have it respecting my color map, or oxygen-gtk and have the oxygen
default color map. Both is visually disappealing..
My humble guess is that Qt5.6 changed the configuration representation for
color settings, resulting in oxygen-gtk using some default values. After
reverting to 5.4.2, all is well again. I've tried a lot to cope with it,
though. Removed ~/.config/Trolltech.conf, fiddled with ~/.gtkrc, GTK2_RC_FILES
and friends, checked the generated color map in ~/.gtkrc, which is fine, etc..
Here's something, that might be useful for others: convert GTK color values to
something, that the rest of the world understands:
$> python3 -c "print([int(255.0*v) for v in (1.000, 0.980, 0.902)])"
Replace the three numbers with some values from ~/.gtkrc, and check the result
in some color choosing widget..
I'm ready and prepared to build some oxygen-gtk packages out of git.
Reproducible: Always
BTW: Hugo, Ruslan, I found some hostility for your project coming from the GTK
camp. Given their unfair behaviour, they deserve, that everybody and their
aunts is using gtk2 still. I assure you, that your code will keep executing on
a lot of systems, since this is one of the rare ways to make this ugly GTK
stuff looking fine. This experience reminded me, how UGLY things could be.
Version: gtk2-{engine,theme}-oxygen-1.4.6, Qt 5.4.2, KDE 4.14 all from openSUSE
13.2.
Qt changed to 5.6.1, built in home:frispete:PyQt5 (based on KDE:Qt on Build
Service).
--
You are receiving this mail because:
You are watching all bug changes.
