GNOME Bugzilla – Bug 475467
crash in System Log: logging out root
Last modified: 2007-09-15 11:54:52 UTC
Version: 2.18.0 What were you doing when the application crashed? logging out root Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 37789696 vsize: 37789696 resident: 12787712 share: 8335360 rss: 12787712 rss_rlim: 4294967295 CPU usage: start_time: 1189429950 rtime: 446 utime: 410 stime: 36 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208670496 (LWP 3148)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 161793
Thread 1 (Thread -1208670496 (LWP 3148))
----------- .xsession-errors (587 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/sehire.harshnet:/tmp/.ICE-unix/2941 ** (gnome-session:2941): WARNING **: Host name lookup failure on localhost. winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running --- Hash table keys for warning below: --> file:///root (nautilus:3351): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** (nautilus:3058): WARNING **: bookmark uri is file:///etc/sysconfig/network-scripts, but expected file:///etc/sysconfig --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 442846 ***