So I found a patch which kills unico's rounded borders management which caused the segfault of gtk3 apps, and I made a pkgbuild to make an "alternative" unico engine. This patch can be found here: https://code.launchpad.net/~robert-ance … rge/110231, and here is the PKGBUILD : http://pastebin.com/uPnqfuYW (some rounded borders won't be rendered with this patched unico engine, so you may have to fix themes to have proper rounded borders).
Thanks, bro. Good job.
]]>@drcouzelis: did you try my modified PKGBUILD to check if it partially solves the problem ?
Good find! I'm sorry, no, I didn't try the modified PKGBUILD file. Instead, I decided last night to uninstall every GTK3 application I was using. It was a lot easier to do than I thought it would be.
]]>This pkgbuild solved the problem for me
]]>So, my suggestion would be, when trying a new or modified theme, to try it on a fresh start, for example, by adding a new temporary user on your computer to try it out.
As for me, I'm considering uninstalling all GTK3 applications...
]]>It's a unico issue, not really a gtk3 one. Hope unico team will fix that for the next release.
]]>Maybe you can add all of your themes to
~/.locale/share/themes
I also found (another) fix when I investigated on the problem (the fixes listed here didn't work for my Zukitwo-Colors themes). The version of gtk-engine-unico in the repositories is built from the revision 139, which did a lot of "removing unused code", which is not really unused (ie code used to draw checkboxes was removed with other useful stuff...).
So I found a patch which kills unico's rounded borders management which caused the segfault of gtk3 apps, and I made a pkgbuild to make an "alternative" unico engine. This patch can be found here: https://code.launchpad.net/~robert-ance … rge/110231, and here is the PKGBUILD : http://pastebin.com/uPnqfuYW (some rounded borders won't be rendered with this patched unico engine, so you may have to fix themes to have proper rounded borders).
]]>Edit: I also cleaned up all the theme parsing errors from gtk-widgets.css. Happy bunny again.
]]>I have had this same issue. To fix it, I simply created ~/.config/gtk-3.0/gtk.css and added:
GtkLabel {
background-color: @transparent;
}This affects/overrides all gtk3 themes.
Works for me.
Thanks!
GtkLabel {
background-color: @transparent;
}
This affects/overrides all gtk3 themes.
]]>in 3.6 theming somewhat changed, first themes need to be in /usr/share/themes, having them in ~/.themes wont work.
Then they seem to have changed some options inside of the themes, which makes 3rd party themes not behave well or not work at all.Install unico engine (bzr) from AUR, this fixes at least a handful of themes. (I know this works for the recently released faience theme)
Dont expect all themes to work tho
I have merged the 'gtk-3.0' folder of my current theme, with the faience theme and at least I can now see the text properly, however my GTK3 apps do look a bit strange now.
I really hope that the GNOME devs will fix this before breaking it (yet) again :-(
anyway, unfortunately you'll probably need to hack on your theme a bit (experiment), wait for an update or look for a gtk 3.6 theme.
It's all "experiment" with me unfortunately If I get the time and inclination I'll have another crack at it. Prompted by the latest breakage I've had another look for a new theme but still can't find one I like.
]]>in 3.6 theming somewhat changed, first themes need to be in /usr/share/themes, having them in ~/.themes wont work.
...or you can still manually copy the theme's gtk-3.0 folder's content to ~/.config/gtk-3.0/ and gtk-2.0 content to ~/.config/gtk-2.0/ - this still works.
]]>Install unico engine (bzr) from AUR, this fixes at least a handful of themes. (I know this works for the recently released faience theme)
Dont expect all themes to work tho
Here's a quick & dirty fix, as mentioned in this article:
when the themes are put in /usr/share/themes instead of ~/.themes, they are handled correctly by Gnome 3.6, and there are no background/window decoration/nautilus glitches...
This is obviously not a good way to proceed, so let's hope that the Gnome dev team fixes this issue soon!
Thats not the case for me. I have all my themes in /usr/share/themes/ and they are broken.
]]>