GNOME Bugzilla – Bug 738981
code-assistance crashes saving a file
Last modified: 2019-03-23 20:54:29 UTC
Fedora 21, yum install gedit gedit-code-assistance, enable code-assistance plugin. open a markdown file (test.md) save crash Program received signal SIGSEGV, Segmentation fault. g_type_check_instance (type_instance=0x1) at gtype.c:4085 4085 if (type_instance->g_class) (gdb) bt
+ Trace 234244
afaik fedora does not provide the new code assistance. If you want to use it you will have to compile it.
The reason for the crash, IIRC, is that the save/load signals have been changed when moving that API from gedit to gsv. Indeed, you'll have to compile gca yourself for now, although it would be nice to release and see it pushed into distro's.
Yes, new releases of {gedit,gnome}-code-assistance is quite important. Jesse, can you do it? Also, it would be simpler to use the same versions as GNOME's and gedit's, so users know which version to install.
I'm currently not able to do a release due to time constraints. I'm fine with bumping the version to match GNOME, if somebody else could do a release that would be great!
Created attachment 291830 [details] 'make distcheck' in gnome-code-assistance fails I've tried to release gnome-code-assistance, but 'make distcheck' fails. I attach the errors. It's most probably a configuration problem with D-Bus. I've just followed the build instructions at: http://blogs.gnome.org/jessevdk/2014/04/11/gnome-code-assistance/ Is there a special thing to do so the D-Bus service works?
gedit- and gnome-code-assistance 3.14.0 have been released, normally this bug is fixed (it works for me).
*** Bug 741526 has been marked as a duplicate of this bug. ***
Filed a bug downstream at https://bugzilla.redhat.com/show_bug.cgi?id=1174356
Can't update the fedora package just yet! The released tarball is broken. If I build the plugin from the released tarball I get this crash just like you'd get with 0.3.1. If I manually clone gedit-code-assistance from git and build it there, it doesn't crash. I think the tarball is broken. If I diff the tarball contents and the generated C files in my fresh clone, I get this: --- ./src/gca-document.c 2014-12-07 21:26:25.000000000 +0200 +++ /home/elad/Sources/gedit-code-assistance/src/gca-document.c 2014-12-16 20:12:05.801624649 +0200 @@ -182,7 +182,7 @@ static void gca_document_on_shortname_changed (GcaDocument* self); static void _gca_document_on_shortname_changed_g_object_notify (GObject* _sender, GParamSpec* pspec, gpointer self); static void gca_document_on_document_saved (GcaDocument* self); -static void _gca_document_on_document_saved_gedit_document_saved (GeditDocument* _sender, GError* _error_, gpointer self); +static void _gca_document_on_document_saved_gedit_document_saved (GeditDocument* _sender, gpointer self); static void gca_document_update_location (GcaDocument* self); static void gca_document_real_dispose (GObject* base); static void gca_document_clear_unsaved_file (GcaDocument* self); @@ -232,7 +232,7 @@ } -static void _gca_document_on_document_saved_gedit_document_saved (GeditDocument* _sender, GError* _error_, gpointer self) { +static void _gca_document_on_document_saved_gedit_document_saved (GeditDocument* _sender, gpointer self) { gca_document_on_document_saved ((GcaDocument*) self); } Perhaps the tarball was generated with an older version of gedit's vapi installed or something like this?
*** Bug 736650 has been marked as a duplicate of this bug. ***
I just made a new relase.