Package: gnome-shell
Version: 3.2.2.1-3
When trying to lad gnome-shell from gdm, it crashes.
I followed instruction for debugging from
http://live.gnome.org/GnomeShell/Debugging
here is the output :
me@debian:~$ ~/xenv.sh
8126
me@debian:~$ gdb gnome-shell
GNU gdb (GDB) 7.4-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/gnome-shell...(no debugging symbols
found)...done.
(gdb) run --replace
Starting program: /usr/bin/gnome-shell --replace
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Gtk-Message: Failed to load module canberra-gtk-module
** (gnome-shell:8323): CRITICAL **: dbus_g_proxy_new_for_name: assertion
`connection != NULL' failed
** (gnome-shell:8323): CRITICAL **: dbus_g_proxy_call: assertion
`DBUS_IS_G_PROXY (proxy)' failed
Program received signal SIGSEGV, Segmentation fault.
0x00402d52 in main ()
(gdb) bt
#0 0x00402d52 in main ()
(gdb) bt
#0 0x00402d52 in main ()
(gdb) t a a bt
Thread 1 (Thread 0x77fa69a0 (LWP 8323)):
#0 0x00402d52 in main ()
(gdb) call gjs_dumpstack ()
$1 = 2
(gdb)
I am using today's latest packages from sid (the bt is from a fully up to
date system).
I did not restart gnome shell or my system for say, a week, so the bug may
not come from latest package releases.
I tried to downgrade gnome-shell and gnome-shell-common to 3.2.2.1-2 (from
wheezy), no luck.
Then I tried to downgrade dbus (even if that no might be a good idea) to
actual wheezy version, same problem .
Finally I downgraded gnome-shell (and according direct dependencies) to
3.2.1-8, as I am sure it was a previous working version.
Still no luck.
That's making me thinking that the bug might not come from gnome-shell
package itself.
Not accessing the computer right now, I will post more information
regarding this bug shortly.