GNOME Bugzilla – Bug 104253
Gnome session crashed
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-session Severity: normal Version: 2.1.90 Synopsis: Gnome session crashed Bugzilla-Product: gnome-session Bugzilla-Component: gnome-session BugBuddy-GnomeVersion: 2.0 (2.1.90) Description: Description of Problem: Gnome-session has crashed in a normal session, there wasn't anything of strange in the desktop using. Debugging Information: Backtrace was generated from '/usr/bin/gnome-session' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1086040960 (LWP 5698)] 0xffffe002 in ?? ()
+ Trace 33057
Thread 1 (Thread 1086040960 (LWP 5698))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-23 12:44 ------- The original reporter (shaihulud@supereva.it) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-session-maint@bugzilla.gnome.org.
Note that bug 104263 looks an awful lot like this one.
*** Bug 111908 has been marked as a duplicate of this bug. ***
This looks the same as bug 105745 (the stack trace of the main thread is identical).
*** Bug 112206 has been marked as a duplicate of this bug. ***
*** Bug 111782 has been marked as a duplicate of this bug. ***
*** Bug 111918 has been marked as a duplicate of this bug. ***
This looks like the mysterious gtk+ crash that is showing up everywhere [See specifically bug 105745 for more info]. A number of people are getting this, but the stack traces are unfortunately useless and we don't know how to reproduce the problem. Can you get a stacktrace with symbols for us? [If you're using RedHat 9, you can do so with the following easy method; otherwise this will require recompiling from source: Install http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm and if the problem occurs again, submit the backtrace you get. Installing the debuginfo package will make the backtrace much more useful.] I am adding myself to the cc and marking as needinfo for now.
*** This bug has been marked as a duplicate of 105745 ***