Created attachment 328076 [details, diff] patch against current unico ebuild The engine crashes if border-top-left-radius is used in a theme. (see https://bugs.launchpad.net/unico/+bug/1000545/comments/13) The latest revision of unico fixes this issue. As ubuntu ships a newer snapshot of unico, most theme authors are not aware of this issue and still use border-top-left-radius.
Created attachment 328078 [details, diff] patch to rev 139 see https://bazaar.launchpad.net/~unico-team/unico/trunk/changes/139?start_revid=139
I can confirm this bug. I'm using: x11-libs/gtk+-3.6.2 x11-libs/cairo-1.12.6 and the themes from lubuntu artwork 0.34: <https://launchpad.net/ubuntu/+source/lubuntu-artwork/0.34> All GTK3 based applications results in segmentation fault.
I confirm this issue, I ran fully into it today. I have updated from gtk+-3.4 to 3.6, which resulted a segmentation fault in every application compiled against gtk+-3
forgot to mention that the output looks similar to this one of gedit: Gtk-Message: Failed to load module "gnomesegvhandler" (gedit:7662): Gtk-WARNING **: Style property "border-top-left-radius" is not gettable (gedit:7662): GLib-GObject-WARNING **: gtype.c:4204: type id `0' is invalid (gedit:7662): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced Segmentation fault
Fixed with gtk-engines-unico-1.0.3_pre20121212, sorry for the wait! +*gtk-engines-unico-1.0.3_pre20121212 (27 Dec 2012) + + 27 Dec 2012; Alexandre Rostovtsev <tetromino@gentoo.org> + gtk-engines-unico-1.0.2.ebuild, +gtk-engines-unico-1.0.3_pre20121212.ebuild: + Add snapshot compatible with gtk+-3.6 (bug #440950, thanks to poncho and + Balint SZENTE). Pin 1.0.2 ebuild to gtk+-3.4-only. Update license.
yep. and the patch included here, fixes this problem. I have tested it myself.
