GNOME Bugzilla – Bug 478315
crash in Tasks:
Last modified: 2007-09-26 05:33:23 UTC
Version: 2.10 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.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 729718784 vsize: 729718784 resident: 86208512 share: 63496192 rss: 86208512 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188378751 rtime: 854 utime: 745 stime: 109 cutime:2 cstime: 7 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 46912508606048 (LWP 14575)] [New Thread 1115699536 (LWP 16219)] [New Thread 1084229968 (LWP 14644)] (no debugging symbols found) 0x0000003791e0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 163959
Thread 3 (Thread 1084229968 (LWP 14644))
----------- .xsession-errors (6 sec old) --------------------- warning: .dynamic section for "/usr/lib64/libgcrypt.so.11" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libgpg-error.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libfam.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libaspell.so.15" 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 462501 ***