GNOME Bugzilla – Bug 455508
crash in System Log:
Last modified: 2007-07-11 10:08:59 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 280076288 vsize: 280076288 resident: 23371776 share: 15151104 rss: 23371776 rss_rlim: 18446744073709551615 CPU usage: start_time: 1184064210 rtime: 1194 utime: 1165 stime: 29 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496319888 (LWP 2445)] (no debugging symbols found) 0x000000310c00d865 in waitpid () from /lib64/libpthread.so.0
+ Trace 146974
Thread 1 (Thread 46912496319888 (LWP 2445))
----------- .xsession-errors (8 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/esllaut:/tmp/.ICE-unix/2211 ** (gnome-system-monitor:2410): WARNING **: SELinux was found but is not enabled. --- Hash table keys for warning below: --> file:///root (nautilus:2472): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) /usr/share/system-config-selinux/system-config-selinux.py:69: Warning: IA__g_object_get_valist: object class `GnomeProgram' has no property named `default-icon' xml = gtk.glade.XML ("/usr/share/system-config-selinux/system-config-selinux.glade", domain=PROGNAME) Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-2448-1879275105-1184064262 --active --geometry 80x24+151+208 --title root@esllaut:~ --work --------------------------------------------------
*** This bug has been marked as a duplicate of 455498 ***