After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 688433 - Shell crashes after enabling extension.
Shell crashes after enabling extension.
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: extensions
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-11-16 01:22 UTC by Lukas Knuth
Modified: 2012-11-18 17:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Lukas Knuth 2012-11-16 01:22:07 UTC
I developed my gnome-shell-extension on gnome-shell 3.4.2 and it worked fine. After updating to gnome-shell 3.6.2, enabling the application (from extensions.gnome.org) causes the shell to crash.

The crash looks (to me) as if the shell is restarting and then I get the error-window which only let's me log out. After logging back in, all extensions are disabled and re-enabling my extension causes the same crash.

I have checked the following files for crash-details, but no luck so far:

* ~/.xsession-errors
* ~/.cache/gdm/session.log
* ~/.cache/gdm/session.log.old

Here are the three above files (xsession-errors is truncated) that where produced right after the error: https://gist.github.com/4083053
Comment 1 Giovanni Campagna 2012-11-16 14:36:16 UTC
From this line:
Log level 16: specified instance size for type `Gjs_StateControlButton' is smaller than `GTypeInstance' size
I reckon this is a duplicate of bug 687184, which is fixed in gjs master.
In any case, the right fix is for the extension not to use derived GTypes (as the extension must be able to be unloaded, and that's not possible for registered types)

*** This bug has been marked as a duplicate of bug 687184 ***
Comment 2 Lukas Knuth 2012-11-18 17:49:58 UTC
Turns out I had a class extend "St.Button" and this class was then extended again by another class (just like in the example of the linked bug).

Not extending the class fixed the problem for me, the changes can be reviewed here: https://bitbucket.org/LukasKnuth/backslide/changeset/561b1dbe542af92ce969bfcecf9e0310b206735f