GNOME Bugzilla – Bug 452786
crash in System Log: logging out as user root
Last modified: 2007-07-01 10:17:31 UTC
Version: 2.18.1 What were you doing when the application crashed? logging out as user root Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 69578752 vsize: 69578752 resident: 21299200 share: 15982592 rss: 21299200 rss_rlim: 4294967295 CPU usage: start_time: 1183284490 rtime: 168 utime: 154 stime: 14 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 -1208428832 (LWP 26593)] (no debugging symbols found) 0x00b42402 in __kernel_vsyscall ()
+ Trace 145029
Thread 1 (Thread -1208428832 (LWP 26593))
----------- .xsession-errors (87 sec old) --------------------- clamav-milter clamav-milter (pid 2130) is running... clamav-milter clamav-milter (pid 26485) is running... CalDAV Eplugin starting up ... --- Hash table keys for warning below: --> file:///root (nautilus:26522): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) evolution-shell-Message: Killing old version of evolution-data-server... (evolution:26506): e-data-server-DEBUG: Loaded default categories ** (evolution:26506): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:26506): DEBUG: mailto URL program: evolution (evolution:26506): e-data-server-DEBUG: Saving categories to "/root/.evolution/categories.xml" --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 421621 ***