Le mercredi 10 juin 2009 à 22:00 +0200, Hanspeter Kunz a écrit : > gnome-session[22686]: WARNING: Unable to parse command '(null)': Key > file contains key 'Terminal' which has value that cannot be interpreted. > gnome-session[22686]: ******************* START > ******************************** > gnome-session[22686]: Frame 0: gnome-session [0x8060685] > gnome-session[22686]: Frame 1: gnome-session [0x8060814] > gnome-session[22686]: Frame 2: [0xb7eff400] > gnome-session[22686]: Frame 3: /usr/lib/libglib-2.0.so.0(g_free+0x36) > [0xb7885cc6] > gnome-session[22686]: Frame 4: /usr/lib/libglib-2.0.so.0(g_strfreev > +0x20) [0xb789e990]
I think I’ve already seen such a bug. It’s related to a desktop file that contains an incorrect "Terminal=" entry. Please look for files violating the spec in /etc/xdg/autostart and /usr/share/gnome/autostart. Of course, gnome-session shouldn’t crash in that case, but that’s what is triggering the bug. Before working around it (by deleting the relevant file), I’d appreciate if you could obtain a backtrace for that issue. To do that, rebuild gnome-session with debugging symbols (see http://wiki.debian.org/HowToGetABacktrace), install libglib2.0-0-dbg, then start a session that only consists of an xterm. In the terminal, run "gdb /usr/bin/gnome-session" and debug it normally as explained in the above wiki page. Cheers, -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling
signature.asc
Description: Ceci est une partie de message numériquement signée
