GNOME Bugzilla – Bug 520727
crash in Tasks:
Last modified: 2008-03-06 12:22:05 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 16:24:29 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 233996288 vsize: 233996288 resident: 83259392 share: 65187840 rss: 83259392 rss_rlim: 4294967295 CPU usage: start_time: 1204795282 rtime: 2945 utime: 2765 stime: 180 cutime:303 cstime: 90 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 -1208461600 (LWP 2986)] [New Thread -1293292656 (LWP 12010)] [New Thread -1270563952 (LWP 3089)] [New Thread -1398424688 (LWP 3036)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191500
Thread 2 (Thread -1293292656 (LWP 12010))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libsoftokn3.so" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libaspell.so.15" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libstdc++.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 445309 ***