GNOME Bugzilla – Bug 322730
GNOME session manager crashed
Last modified: 2006-01-23 09:40:30 UTC
Distribution: Unknown Package: gnome-session Severity: Normal Version: GNOME2.12.0 unspecified Gnome-Distributor: SUSE Synopsis: GNOME session manager crashed Bugzilla-Product: gnome-session Bugzilla-Component: gnome-session Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: When trying to log out, session-manager crashed Steps to reproduce the crash: 1. Suspend the computer 2. Resume the computer 3. Session manager seems unstable then Expected Results: Session manager is stable How often does this happen? Once so far Additional Information: After resume I had several "Information" windows appearing without displaying any contents. So I wanted to restart the computer. Debugging Information: Backtrace was generated from '/opt/gnome/bin/gnome-session' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) (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) (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) (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) (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) (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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 1089891200 (LWP 1123)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 64323
Thread 1 (Thread 1089891200 (LWP 1123))
------- Bug moved to this database by unknown@gnome.bugs 2005-11-29 07:58 UTC -------
Version is SUSE Linux 10.0.
can you install the liborbit debug package please, and repost the stack trace? 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.
*** Bug 327898 has been marked as a duplicate of this bug. ***
trace similar to Bug 146075
I hope this will do. Backtrace was generated from '/usr/libexec/trashapplet' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1224264000 (LWP 7245)] [New Thread -1227064400 (LWP 7246)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 65462
Thread 2 (Thread -1227064400 (LWP 7246))
yes, thanks Danilo. confirming report. looks like ORBit_handle_request() calls ORBit_adaptor_find() with adaptor = (ORBit_ObjectAdaptor) 0x0
fix back-ported to the gnome-2-12 branch - thanks for the report.
of course - quite why we suddenly start getting these invalid object references coming in left & right, I have no idea ;-) clearly something odd there. Perhaps it's re-using a socket where it used not to before - that'd be odd though.