GNOME Bugzilla – Bug 356857
gnome-session crash & unable to get a stack trace
Last modified: 2006-10-27 12:09:31 UTC
Steps to reproduce: After 3-4 hours of working I get a random application crash and I'm unable to start a new desktop application. bug-buddy starts, but it cannot be shown too, so I miss the trace. The only option is to restart X11. Stack trace: ps axfww gives the following output .... 26182 ? Ss 0:00 \_ gnome-session 26202 ? Ss 0:00 \_ /usr/bin/ssh-agent -- gnome-session 3922 ? S 0:00 \_ /usr/libexec/gnome_segv gnome-session 11 2.16.0 3925 ? S 0:00 \_ /usr/bin/bug-buddy --appname=gnome-session --pid=26182 --package-ver=(null) .... 26236 ? Ss 0:04 gnome-power-manager 3923 ? S 0:00 \_ /usr/libexec/gnome_segv gnome-power-manager 11 2.16.0 3924 ? S 0:00 \_ /usr/bin/bug-buddy --appname=gnome-power-manager --pid=26236 --package-ver=(null) .... 3921 ? S 0:00 /usr/libexec/gnome_segv epiphany 11 2.16.0 3926 ? S 0:00 \_ /usr/bin/bug-buddy --appname=epiphany --pid=3006 --package-ver=(null) what is in ~/.xsession-errors /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/X11/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "kirov" /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session SESSION_MANAGER=local/kirov:/tmp/.ICE-unix/3985 Gnome-Message: gnome_execute_async_with_env_fds: returning -1 seahorse nautilus module initialized (gnome-panel:4035): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed Other information: system is Gentoo GNU/Linux gnome-session-2.16.0 gdm-2.16.0-r1 libgnome-2.16.0 bug-buddy-2.16.0 I tryied to remove package bug-buddy. When the crash happen I get and error dialog, which says that session will be restarted.
During the crash '/tmp/.ICE-unix/PID' socket is not responsible $ strace epiphany ...... rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0 mkdir("/home/kirov/.gnome2", 0700) = -1 EEXIST (File exists) mkdir("/home/kirov/.gnome2_private", 0700) = -1 EEXIST (File exists) chmod("/home/kirov/.gnome2_private/", 0700) = 0 mkdir("/home/kirov/.gnome2/accels", 0700) = -1 EEXIST (File exists) gettimeofday({1158745214, 28368}, NULL) = 0 gettimeofday({1158745214, 28793}, NULL) = 0 gettimeofday({1158745214, 28873}, NULL) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 10 uname({sys="Linux", node="kirov", ...}) = 0 connect(10, {sa_family=AF_FILE, path="/tmp/.ICE-unix/26032"}, 22) = 0 fcntl64(10, F_SETFD, FD_CLOEXEC) = 0 write(10, "\0\1\0\0\0\0\0\0", 8) = 8 read(10, - waits forever
Once again I had a crash and managed to get a stacktrace from epiphany proccess (gdb) thread apply all bt full
+ Trace 72894
Is it possible epiphany to cause the crash of gnome-session ?
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Also, we'd love a stack trace of gnome-session, since this is the main issue here. You'll probably need to run gnome-session from the console in gdb, though.
The only debug trace that I can get is similar to the one in Bug 358263 .Could you point me to a command line for running gnome-session + dbus-daemon + ssh-agent in gdb? I tried it with startx, but after "run" the login process hang up forever. gdb trace: (gdb) thread apply all bt full
+ Trace 74041
Thread 1 (Thread -1223444816 (LWP 6171))
Detaching from program: /usr/bin/gnome-session, process 6171
ssh-agent and dbus-daemon only set environment variables, I believe. You can launch them and set the correct variables or launch them with bash as a command to launch. Then "gdb gnome-session" :-)
Cannot reproduce the crash anymore. Meanwhile dbus has been upgraded to 0.94 and gnome-session is 2.16.1
Well, let's close the bug then. If this happens again, feel free to reopen :-) Thanks