Re: debug X errors?

[Milan Bouchet-Valat <nalimilan club fr>]

Le dimanche 29 août 2010 à 13:38 -0700, Luis Villa a écrit :
> Hey, guys-
> The latest stuff is looking pretty nice, but unfortunately it is also
> crashing pretty regularly for me, with errors like the following:
> 
> Bug in window manager: Unexpected X error: BadDrawable (invalid Pixmap
> or Window parameter) serial 26638 error_code 9 request_code 136
> minor_code 4)
> Shell killed with signal 6
I'm seeing the same crash at the moment, with an Intel card too. It's pretty recent,
so don't worry, it may go away quickly too!

Seems to be related to
https://bugzilla.gnome.org/show_bug.cgi?id=626556
but the reporter closed the bug.

> Any pointers on how to debug those?
I'd say first report it in Bugzilla, and people will tell you how to
debug. Generally, you can run gnome-shell with -g, and it will run in a
gdb session, where you'll be able to get a stacktrace. For X issues,
runnning with --sync is a good idea.

> Also, is there any way to
> automatically restart shell instead of falling back to metacity when
> this kind of thing happens?
If you copy data/gnome-shell.desktop to ~/.config/autostart to run the
Shell when starting the session, it will restart automatically instead
of Metacity.

Regards