GNOME Bugzilla – Bug 756338
applications segfaults on 3.18.1 when using external themes
Last modified: 2015-10-14 10:34:55 UTC
Hi, starting with 3.18, using evolution with Greybird theme leads to segfault. The downstream bug is at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800911 Switching to Adwaita leads to no segfault, so I assume something changed in theme handling, breaking the API, intentionaly or not. The Greybird theme can be found at https://github.com/shimmerproject/Greybird Here's the backtrace (I've dropped the debubgging symbols for evolution and evolution-data-server because I assume they're not relevant but please ask if they are). Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 235565
I was asked to provide a backtrace from a run with G_DEBUG="fatal-criticals" so here it is:
+ Trace 235566
The backtrace shows: prop_name = 0x3787b9dfb65 "link-color" which is indeed present in Greybird, but apparently not in Adwaita. That would explain why the assertion is not triggered there.
Created attachment 313020 [details] minimal reproducer The problem here is the combination of a style property with a symbolic color.
And where is the problem lying then? In GTK+ or in the themes?
It's a regression in gtk+
git bisect told me: 3e5280ae4dfd1950dbd56a781dcdcf34a26d4294 is the first bad commit commit 3e5280ae4dfd1950dbd56a781dcdcf34a26d4294 Author: Benjamin Otte <otte@redhat.com> Date: Mon Apr 27 19:15:43 2015 +0200 stylecontext: Clear style property more frequently We want to clear the style property cache whenever things change in the tree, not as we previously did only when those changes actually lead to a different CSS style.
Should be fixed by https://git.gnome.org/browse/gtk+/commit/?id=bddc524cd84b76d1c25c7700eca9d3a25db30cf6
*** Bug 756508 has been marked as a duplicate of this bug. ***