GNOME Bugzilla – Bug 477024
crash in Tasks: nothing
Last modified: 2007-10-11 17:07:17 UTC
Version: 2.10 What were you doing when the application crashed? nothing 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.22.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 609431552 vsize: 609431552 resident: 57217024 share: 45993984 rss: 57217024 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189798659 rtime: 59 utime: 50 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 46912514773776 (LWP 31945)] [New Thread 1136679248 (LWP 31960)] [New Thread 1126189392 (LWP 31952)] [New Thread 1105209680 (LWP 31950)] [New Thread 1084229968 (LWP 31948)] (no debugging symbols found) 0x0000003228e0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 162972
Thread 1 (Thread 46912514773776 (LWP 31945))
----------- .xsession-errors (28648 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/peter --> file:///home/peter/archive (nautilus:28953): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 2 elements at quit time (keys above) --- Hash table keys for warning below: --> file:///home/peter --> file:///home/peter/archive (nautilus:29170): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 2 elements at quit time (keys above) closing closing --------------------------------------------------
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 364700 ***