GNOME Bugzilla – Bug 475635
crash in Tasks: absolutely nothing. idl...
Last modified: 2007-09-23 13:38:25 UTC
What were you doing when the application crashed? absolutely nothing. idle with the inbox selected 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Crux Memory status: size: 139313152 vsize: 139313152 resident: 37875712 share: 21667840 rss: 37875712 rss_rlim: 4294967295 CPU usage: start_time: 1189453803 rtime: 4128 utime: 3157 stime: 971 cutime:77 cstime: 24 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208633632 (LWP 5583)] [New Thread -1284453488 (LWP 11934)] [New Thread -1263080560 (LWP 5615)] [New Thread -1273963632 (LWP 5612)] [New Thread -1225147504 (LWP 5602)] (no debugging symbols found) 0x004c2402 in __kernel_vsyscall ()
+ Trace 161904
Thread 2 (Thread -1284453488 (LWP 11934))
----------- .xsession-errors --------------------- warning: .dynamic section for "/lib/libattr.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libacl.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libfam.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libbeagle.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 460409 ***