Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
[solved?] New GTK2 bug? Maybe it's a QtCurve bug. Theme changes randomly
UPDATE: whatever happened before, it seems that now it can be partly solved by simply commenting out the font-related lines in /usr/share/themes/QtCurve/gtk-2.0/kdeglobals (not to be confused with KDE's own file with the same name!).
After a while (after a massive upgrade) the randomness of the thing stopped, the correct theming consistently fails. More evidently fonts, icon theme, and colors (including tooltips' colors). I'm not sure the widget's "design" is also affected, I think it's not, or at least the defaults is very flat and square, and easy to confuse with my custom theme.
The same trick/fix that works with the fonts doesn't seem to affect icon theme or colors, but the icon theme can at least be manually set on the same file, as long as all users using QtCurve want the same icon theme.
Bug Report for Ubuntu, which ignores the icon theme and color issues:
https://bugs.launchpad.net/ubuntu/+s...e/+bug/1078446
That probably "settles" it, until the next upgrade, if it's not fixed more properly. I'll leave the earlier version of the post "archived" below, just in case.
_______________________________________________
Well, not totally "randomly", it seems it always "falls back" to a specific theme whose name I don't know, not to any random theme from the whole pool of themes.
I think that it has been a week or so that the GTK2 apps will randomly/sometimes use one other theme than what I use (qtcurve), even though I've exported the GTK2_RC_FILES or whatever in every possible moment imaginable (even though I'm not sure i saw it happen with export "GTK2=whatever && gtk2app", but maybe even then).
Well, namely in .xinit, .xsession, .profile, openbox' "environment" and autostart, KDE's "env" scripts (even though I really only use openbox).
I run GTK2app, comes with the wrong theme; close it, run it again with the same exact command, from the same exact place, comes with the correct theme the second time. I never saw anything like this.
It may be something wrong actually with KDE. I think in some recent update there were a bunch of KDE-related stuff being upgraded, and, after that, more rarely the GTK3 theme will also sometimes (may have happened like three times over two weeks) change by itself, but actually changing the config files instead of being a crazier "runtime" bug. But perhaps that's partly an "illusion" from having done something like running ksystemsettings5, set the GTK3 theme, run some GTK3 app, then running lxappearence, and changing something that one would thought was unrelated, but that unadvertisedly affects the GTK3 config set by KDE too.
I'm not posting it on the forums because I'm not terribly worried or annoyed by that. It could even be the result of a messy $USER folder configs and scripts, which wouldn't happen with a brand new default/more carefully customised user. I think I'll try that sometime, if anyone reading this is having the same issue, I'd suggest to try to go to that route first, unless there is something much more likely to work than I'm missing. Perhaps just renaming/moving the theme files and folders to backups instead of creating a brand new user, which may be somewhat less bothersome.
__________________________________
Using the daemon xsettingsd doesn't fix it. Also, it can't set different themes for GTK2 and 3. If QtCurve (GTK2) is set, GTK3 defaults to Adwaita, overriding the settings configured elsewhere.
__________________________________
I think some of this default style is coming from /usr/share/themes/QtCurve/gtk-2.0/kdeglobals
(not to be confused with KDE's own file with the same name!)
I've found about this file searching for bugs with QtCurve, which is perhaps the culprit, not GTK2.
I've edited the font on that file and then the wrong theme sometimes popped up with the correct font, but the wrong icons and everything else.
I don't get how it works, when and where it looks for the user files for the customised/chosen QtCurve "sub" theme. I think it's not doing that fast enough, or always.
I think I may have solved it! One of the possibly redundant gtkrc-2.0 files, gtkrc.mine, (which is perhaps "included" in one of the others), had the gtk style set to "qtcurve", all lowercase, instead of "QtCurve". It may be too soon to be sure it's really working, but it does look so.
Not really. Just one fluke followed by another.
After a while (after a massive upgrade) the randomness of the thing stopped, the correct theming consistently fails. More evidently fonts, icon theme, and colors (including tooltips' colors). I'm not sure the widget's "design" is also affected, I think it's not, or at least the defaults is very flat and square, and easy to confuse with my custom theme.
The same trick/fix that works with the fonts doesn't seem to affect icon theme or colors, but the icon theme can at least be manually set on the same file, as long as all users using QtCurve want the same icon theme.
Bug Report for Ubuntu, which ignores the icon theme and color issues:
https://bugs.launchpad.net/ubuntu/+s...e/+bug/1078446
That probably "settles" it, until the next upgrade, if it's not fixed more properly. I'll leave the earlier version of the post "archived" below, just in case.
_______________________________________________
Well, not totally "randomly", it seems it always "falls back" to a specific theme whose name I don't know, not to any random theme from the whole pool of themes.
I think that it has been a week or so that the GTK2 apps will randomly/sometimes use one other theme than what I use (qtcurve), even though I've exported the GTK2_RC_FILES or whatever in every possible moment imaginable (even though I'm not sure i saw it happen with export "GTK2=whatever && gtk2app", but maybe even then).
Well, namely in .xinit, .xsession, .profile, openbox' "environment" and autostart, KDE's "env" scripts (even though I really only use openbox).
I run GTK2app, comes with the wrong theme; close it, run it again with the same exact command, from the same exact place, comes with the correct theme the second time. I never saw anything like this.
It may be something wrong actually with KDE. I think in some recent update there were a bunch of KDE-related stuff being upgraded, and, after that, more rarely the GTK3 theme will also sometimes (may have happened like three times over two weeks) change by itself, but actually changing the config files instead of being a crazier "runtime" bug. But perhaps that's partly an "illusion" from having done something like running ksystemsettings5, set the GTK3 theme, run some GTK3 app, then running lxappearence, and changing something that one would thought was unrelated, but that unadvertisedly affects the GTK3 config set by KDE too.
I'm not posting it on the forums because I'm not terribly worried or annoyed by that. It could even be the result of a messy $USER folder configs and scripts, which wouldn't happen with a brand new default/more carefully customised user. I think I'll try that sometime, if anyone reading this is having the same issue, I'd suggest to try to go to that route first, unless there is something much more likely to work than I'm missing. Perhaps just renaming/moving the theme files and folders to backups instead of creating a brand new user, which may be somewhat less bothersome.
__________________________________
Using the daemon xsettingsd doesn't fix it. Also, it can't set different themes for GTK2 and 3. If QtCurve (GTK2) is set, GTK3 defaults to Adwaita, overriding the settings configured elsewhere.
__________________________________
I think some of this default style is coming from /usr/share/themes/QtCurve/gtk-2.0/kdeglobals
(not to be confused with KDE's own file with the same name!)
I've found about this file searching for bugs with QtCurve, which is perhaps the culprit, not GTK2.
I've edited the font on that file and then the wrong theme sometimes popped up with the correct font, but the wrong icons and everything else.
I don't get how it works, when and where it looks for the user files for the customised/chosen QtCurve "sub" theme. I think it's not doing that fast enough, or always.
I think I may have solved it! One of the possibly redundant gtkrc-2.0 files, gtkrc.mine, (which is perhaps "included" in one of the others), had the gtk style set to "qtcurve", all lowercase, instead of "QtCurve". It may be too soon to be sure it's really working, but it does look so.
Not really. Just one fluke followed by another.
Total Comments 3
Comments
-
deletedPosted 09-01-2015 at 02:31 AM by the dsc 
Updated 09-07-2015 at 01:35 AM by the dsc -
deleted
Posted 09-01-2015 at 07:39 PM by the dsc
Updated 09-07-2015 at 01:35 AM by the dsc -
deleted -- added to the body of the post as an edition. I had the impression I couldn't edit anymore after a short time, but it's not so.
Posted 09-07-2015 at 01:29 AM by the dsc
Updated 09-07-2015 at 01:36 AM by the dsc
