I’ve recently switched from the 13.2 and have found that the GTK3 apps look strange now. Is it a common problem?
mine looks like that too… but if I oipen an app that uses it, like Audacious, it looks fine and good just like always. So maybe the issue is limited only to the preview in the settings
No, all GTK3 apps I have installed look like on the preview: pavucontrol, emacs-x11, and gramps.
Might be because GTK3 completely dropped support for theming engines:
https://bugzilla.gnome.org/show_bug.cgi?id=735211
https://bugs.kde.org/show_bug.cgi?id=343555
https://forum.kde.org/viewtopic.php?f=285&t=125246
It works fine here in 13.2, including the preview:
yes indeed, PAVUcontrol looks weird… I tried gedit and it was horrible looking too, but other apps have the oxygen look, I wonder why this could happen. Have you got GNOME installed on the same machine?
Are you sure all those “other apps” are actually using GTK3?
Audacious e.g. uses GTK2, which is not affected.
They only removed theming engine support from GTK3, which breaks Oxygen for all GTK3 applications obviously.
I wouldn’t understand either why one app would work and others not…
yep, the thread with Hugo Perreira is particulary relevant
Wolfi, I checked all the GTK3 apps look weird… GTK2 are all ok… my solution was to remove the gtk-kde-config utility from KDE and I’m happier with the result.
I’m having some strange things happen when logging into GNOME these days, very slow starts… if I check my resources it seems like very little is being used (12% RAM) low CPU, but still everything runs slow too. Not sure what the cause is or where to look
Why uninstall it?
You could just as well set a different GTK3 theme in “Configure Desktop”->“Application Appearance”->GTK.
Uninstalling kde-gtk-config removes this settings module completely, and makes it impossible to configure the GTK2 and GTK3 style in KDE.
I’m having some strange things happen when logging into GNOME these days, very slow starts… if I check my resources it seems like very little is being used (12% RAM) low CPU, but still everything runs slow too. Not sure what the cause is or where to look
Graphics driver problem maybe? GNOME uses OpenGL unconditionally, and that can rapidly slow it down if it has to fall back to Mesa’s software renderer.
The kde-gtk-config or its settings should have absolutely no influence on GNOME itself though, so even if you set Oxygen as GTK3 theme there, GTK3 applications will look fine in GNOME, unless you set Oxygen as theme in GNOME’s settings themselves.
IOW, I think you should open a new thread for that problem.
Related problem I think: toolbar icons size now is very large in GTK3 apps, this recipe doesn’t help: https://askubuntu.com/questions/201987/how-do-i-force-a-16x16-icon-size-for-toolbar-icons-in-gtk-3[IMG]http://susepaste.org/view/raw/50447958
Well, of course I had already tried that but the GTK 3 themes are all looking ****, the transparency is showing as black… Anyway. uninstalling the kde-gtk-config worked like a charm: it retained the GTK2 oxygen theme and GTK3 are using the GNOME default (adwaita) and I can live with that.
I’m using proprietary drivers, but GNOME 3:16 is working very well and fast too, for that matter. I quite like it. I am now relying on GNOME more than KDE. Maybe in the future I’ll do a clean install of PLASMA5 (when it’s better worked out) and remove GNOME altogether. I use 2 machines for my work, so my priority is keeping the apps and devices running. But thanks for the tips.
But kde-gtk-config is just the config module.
It does nothing else than create a ~/.config/gtk-3.0/settings.ini with its corresponding theme settings. Is that broken too with the latest GTK3?
(I am not using Tumbleweed myself, and in my test VM I have only installed KDE)
I’m using proprietary drivers, but GNOME 3:16 is working very well and fast too, for that matter.
So it just takes long to start?
Are you using Auto-Login? I remember a bug report about some race-condition that caused GNOME to take a long time to start with Auto-Login.
I think maybe the issue only arises when one has the two shells (plasma and gnome) installed. It wasn’t an issue before 3.16 either. I didn’t encounter this effect with 3.14.
To be clear since I have only GNOME on my machine now, everything runs as expected. Startup is fast. BTW I only ever use manual login. Especially being on Tumbleweed that is recommendable, makes it easier to address any issues like reinstalling or patching the NVIDIA display drivers after a kernel update, as well as other things.
Yeah, it works fine here on 13.2 with 3.14, even the GTK3 Oxygen theme.
It shouldn’t make a difference whether you have the GNOME shell installed or not though. Again, kde-gtk-config is just the configuration module, and the generated gtk3-config should not even be used inside GNOME.
If there is a problem with GTK 3.16 (like the generated config not working correctly as you seem to indicate), this might be worth a bug report at http://bugs.kde.org/.
To be clear since I have only GNOME on my machine now, everything runs as expected. Startup is fast.
Well, if you only have GNOME, you don’t need kde-gtk-config anyway of course.
no, not any more, but the original poster had a point… and yes, I agree with you, obviously.
It all works well together under the official release 13.2 but the purpose of Tumbleweed is to identify possible issues, or not?
If people don’t try things out, you’ll never know, right? but KDE is the real house of innovation IMHO… GNOME, they have a core of paid developers, but KDE is everybody and anybody yet it has so many really great apps and innov…well, how to synchronize and take the best out of it all? a pity that some people demean QT… sorry, I apologise to be expressing so many opinions here where the real issue is technical… yet, the opinions are actually based on experience and technicalities