GNOME Bugzilla – Bug 58844
the session manager crashed (i guess)
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-core Severity: normal Version: 1.2.4 Synopsis: the session manager crashed (i guess) Class: sw-bug Distribution: Red Hat Linux release 7.0 (Guinness) System: Linux 2.2.17-14 i586 unknown C library: glibc-2.2-12 C compiler: 2.96 glib: 1.2.8 GTK+: 1.2.8 ORBit: ORBit 0.5.6 gnome-libs: gnome-libs 1.2.8 libxml: 1.8.10 gnome-print: gnome-print-0.25-8_helix_1 gnome-core: gnome-core 1.2.4 Description: the session manager crashed, for no obvious reason. right before this happened, the display greyed out and displayed the "are you sure you want to logout?" dialog. i'm not sure why this happened, unless i accidently hit a key which provoked it. but i clocked on the "cancel" button. i suspect the X server (an ethernet connected NCD X terminal) ran out of memory for new windows and stuff. it was quite low on memory, though not completely out. it has 16 Mbyte of ram. the LInux box is a 120 MHz Pentium with 32 Mbyte of ram and a lot of swap space. it might have been performance or memory constrained as well. Debugging information: (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)...0x40591869 in __wait4 () from /lib/libc.so.6
+ Trace 8335
------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-08-11 02:20 ------- The original reporter (charmer@punchdown.org) 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-core-maint@bugzilla.gnome.org.
Please upgrade to the latest packages and see if that fixes it for you. Your release is fairly old by now.
*** This bug has been marked as a duplicate of 38666 ***