GNOME Bugzilla – Bug 757240
gedit and spacefm crashed in a gtk3 call.
Last modified: 2015-10-28 18:40:39 UTC
Created attachment 314300 [details] gedit backtrace. The spacefm and gedit applications crashed at start in a gtk3 library call. The problem is described here: https://bugs.archlinux.org/task/46839 backtrace from gedit attached.
Arch distro, gtk3 version 3.18.2
Thanks for taking the time to report this. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so and reopen this bug report. Thanks in advance!
done.
Created attachment 314305 [details] backtrace from gedit with debug symbols included
+ Trace 235641
Re-opening; thanks for the updated stack trace!
There seem to be a parsing error trying to bubble up. Are you using Adwaita? Are you using any customisations on top of the theme? Are there any other errors printed out in the session log, or on the terminal, if you launch gedit/spacefm manually?
So, I localized the problem. I have had a custom gtk.css in a ~/.config/gtk-3.0 (I attach it now). But there were no problems before.
Created attachment 314329 [details] gtk "custom" css
And there are no another errors printed out. Only the crash report in dmesg.
Malformed CSS should definitely not make GTK crash.
If I remove that file, there no more problems. So, it must be truly parser problem.
Please, don't close the bug report: we're going to use it to track why the parser is breaking.
commit a58d8bdcbc291818ce70cf3e3fcb93e762ca9c36 Author: Benjamin Otte <otte@redhat.com> Date: Wed Oct 28 19:35:23 2015 +0100 cssprovider: Have a section when parsing style properties Signal handlers expect a section to be present, so provide them with one. New testcase included.