On Wed, Apr 28, 2010 at 04:51:19PM +0200, Josselin Mouette wrote: > Le mercredi 28 avril 2010 à 16:30 +0200, Jan Hauke Rahm a écrit : > > > FYI, you can work around it by > > > setting /desktop/gnome/interface/accessibility to false > > > in /etc/gdm3/greeter.gconf-defaults (but obviously we should fix this > > > instead). > > > > That makes gdm3 start again, yes, but the panels won't come up, so the > > session is pretty unusable. > > Which session? The one internal to gdm? Are there other error messages > in the logs in this case?
Didn't find anything. Interestingly it now works. Maybe it kicked something else off. I even had to kill gnome-panel once when it used 100% of one of my CPU cores. Anyways, with your workaround gnome starts now and runs. > > > > Feel free to ping me for more information. > > > > > > To go further, installing libatspi-dbg should give a more detailed > > > backtrace. Ideally if you managed to run the gnome-session process that > > > crashes in a gdb session you could obtain an even more detailed one. > > > > Erm, I'm not very familiar with C/C++ debugging, so don't hit me -- but > > how exactly am I supposed to attach gdb to gnome-session if gnome > > restarts every one and a half seconds? > > If you start gdm in a gdb process, it should be able to trap crashes > from the programs it is running. Hmm, I only got attached file from running 'gdb gdm3'. I'm possibly doing this completely wrong, though :) Hauke -- .''`. Jan Hauke Rahm <j...@debian.org> www.jhr-online.de : :' : Debian Developer www.debian.org `. `'` Member of the Linux Foundation www.linux.com `- Fellow of the Free Software Foundation Europe www.fsfe.org
signature.asc
Description: Digital signature
