GNOME Bugzilla – Bug 576766
Configuring "Draw Spaces" crashes Gedit
Last modified: 2019-03-23 20:48:22 UTC
Steps to reproduce: 1. Go to plugins tab in Gedit 2. (Tick,) untick, tick "Draw Spaces" 3. Open the configure frame and change the state of any checkbox Stack trace:
+ Trace 213856
Other information: The failing cast happens in the on_gconf_notify function at GeditDrawspacesPlugin *plugin = GEDIT_DRAWSPACES_PLUGIN (user_data); in /plugins/drawspaces/gedit-drawspaces-plugin.c Even if every option is ticked and the plugin is active, it doesn't draw spaces - but I don't know if that's connected.
Thanks for taking the time to report this bug. 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 http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Sorry, c&p error.
+ Trace 213860
Strange symbols - got it from a CoreDump using gdb. I now crashed gedit directly via gdb and got this stack trace:
+ Trace 213862
Additional info: I can't reproduce this bug on gedit 2.24.2
I'm sure that's because 2.24.2 uses the older python version of "Draw Spaces" (which worked fine btw.).
Which gtksourceview version do you have?
On Ubuntu Jaunty Beta: libgtksourceview1.0-0 is on 1.8.5-2 libgtksourceview2.0-0 is on 2.6.0(-0ubuntu2)
I can confirm this on Ubuntu Jaunty beta - but it doesn't always do it - probably about 50% of the time; I got it when I clicked on draw tabs (maybe the 2nd time?) package versions (all Ubuntu 64bit): gedit 2.26.0-0ubuntu2 gedit-plugins 2.26.0-0ubuntu3 libgtksourceview2.0-0 2.6.0-0ubuntu2 libgtksourceview1.0-0 1.8.5-2 With ubuntu system uptodate as of today. Dave Backtrace: Program received signal SIGSEGV, Segmentation fault.
+ Trace 213950
Thread 140344653146064 (LWP 26046)
Created attachment 131604 [details] [review] drawspaces This should fix the bug.
Yes, can't crash it like before. :) Unfortunately this didn't fix the plugin not drawing any spaces. A different bug then. Tested the other plugins the same way (enable, disable, reenable) and it seems charmap is another candidate (the other C plugins bookmarks and showtabbar are ok). Won't crash but freeze the application and gedit spits out those msgs: GLib-GObject-WARNING **: cannot register existing type `GucharmapChaptersView' GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed Should I file a new bug for this too?
(In reply to comment #10) > Yes, can't crash it like before. :) > > Unfortunately this didn't fix the plugin not drawing any spaces. A different > bug then. Do you have the View->Show White Spaces option enabled? > > Tested the other plugins the same way (enable, disable, reenable) and it seems > charmap is another candidate (the other C plugins bookmarks and showtabbar are > ok). Won't crash but freeze the application and gedit spits out those msgs: > > GLib-GObject-WARNING **: cannot register existing type `GucharmapChaptersView' > GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' > failed > GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT > (object_type)' failed > > Should I file a new bug for this too? >
> Do you have the View->Show White Spaces option enabled? I'm not feeling very smart right now. :D
I've commited a patch to fix drawspaces, now I'll check what's the problem with charmap. If you realize about another plugin, please tell us.
Thanks for your efforts! No, I couldn't find any related problems with the other plugins. About the "View > Show White Spaces"-option: I think it's more reasonable to have this option enabled by default like it was with the python version. If a user activates a plugin he usually wants it to be ready to use without having to activate it a second time via the menu.
(In reply to comment #14) > Thanks for your efforts! > > No, I couldn't find any related problems with the other plugins. > > About the "View > Show White Spaces"-option: I think it's more reasonable to > have this option enabled by default like it was with the python version. If a > user activates a plugin he usually wants it to be ready to use without having > to activate it a second time via the menu. > Done. This bug should be finally fixed.