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 677850 - Crash when running Gimp in non-fallback mode
Crash when running Gimp in non-fallback mode
Status: RESOLVED NOTGNOME
Product: gnome-shell
Classification: Core
Component: extensions
3.4.x
Other Linux
: High critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-06-11 11:51 UTC by Jan Rüegg
Modified: 2012-06-12 12:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Crash when trying to use --replace in debugger (5.59 KB, text/plain)
2012-06-11 13:42 UTC, Jan Rüegg
Details

Description Jan Rüegg 2012-06-11 11:51:59 UTC
As described here:
https://bugs.archlinux.org/task/30137

gnome-shell crashes when gimp (or some other programs, like LibreOffice) are opened. The whole shell (except the mouse pointer) and all applets freeze, CPU spikes to 100% (50 from Xorg, 50 from gnome-shell), and the Xserver has to be restarted.

Using a 64-bit Archlinux with these software versions:

extra/gimp 2.8.0-2
extra/gnome-shell 3.4.1-3 (gnome)
extra/nvidia 295.53-1

and graphics card:

NVIDIA Corporation GT200b [GeForce GTX 275]

Strangely, starting "gimp" in a terminal works, while "gimp-2.8" makes everything crash. (Even though gimp is only a symlink to gimp-2.8)

Dmesg gives a warning like this whenever this happens:
[ 1060.949838] gnome-shell-cal[3861] trap int3 ip:7fe930cc25e1 sp:7fff8958b0e0 error:0

Also, when running in fallback mode, everything works fine, and none of this reproducible crashes happen at all.
Comment 1 Florian Müllner 2012-06-11 12:07:53 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see   https://live.gnome.org/GnomeShell/Debugging for more information on how to do so. Thanks in advance!
Comment 2 Jan Rüegg 2012-06-11 13:41:58 UTC
I tried to do the stack trace, but the instructions you gave me do not work:
The problem is the third step:

- Doing a "gdb attach $(pidof gnome-shell)" makes the gnome-shell go black and unresponsive, except for the mouse that can still move
- Doing a "./src/gnome-shell --replace -g" in the compiled sources gives the error
/home/jrueegg/tmp/shell/src/gnome-shell-3.4.1/src/.libs/lt-gnome-shell-real: Unknown option -g
- And finally, doing a "$ gdb /usr/bin/gnome-shell" and "(gdb) run --replace" makes it segfault: (see attached log)
Comment 3 Jan Rüegg 2012-06-11 13:42:25 UTC
Created attachment 216116 [details]
Crash when trying to use --replace in debugger
Comment 4 Jan Rüegg 2012-06-11 13:56:21 UTC
One more thing: I just found out that it only crashes when this extension is enabled:
https://extensions.gnome.org/extension/39/put-windows/

So maybe a bug in the extension ... ?
Comment 5 Jan Rüegg 2012-06-11 14:06:27 UTC
Bug report opened for extension:

https://github.com/negesti/gnome-shell-extensions-negesti/issues/13
Comment 6 Jasper St. Pierre (not reading bugmail) 2012-06-11 14:06:54 UTC
There seems to be two separate crashes here, correct? One on startup with gdb, and one when starting GIMP. Which one is related to the put-windows extension?
Comment 7 Jan Rüegg 2012-06-11 14:08:38 UTC
You're right, I wasn't clear. The original problem (freeze when starting gimp) is solved when disabling the extension.

I didn't try the gdb stuff without the extension...

Can anyone else reproduce the bug when installing the put-windows extension?
Comment 8 Jan Rüegg 2012-06-12 09:24:21 UTC
The bug is fixed... it seems to have been an extension problem:
https://github.com/negesti/gnome-shell-extensions-negesti/issues/13
Comment 9 clemens 2012-06-12 10:53:36 UTC
The problem was that i added a helper method to show a Gtk MessageBox. This works fine when editing prefs but produces an uncought exception when called from the extension. Creating a Gtk.MessagDialog with LookingGlas has the same effect:

    var md = new Gtk.MessageDialog({
      modal:true,
      message_type: Gtk.MessageType.INFO,
      buttons:Gtk. ButtonsType.OK,
      title: "title",
      text: "message"
    });

    md.run();
    md.destroy();
Comment 10 Florian Müllner 2012-06-12 12:17:41 UTC
Yes, you can't open normal (read: non-override-redirect) windows from the window manager. In general I'd advice strongly against using GTK+ in extensions (except for preferences of course, which are run as separate process).