GNOME Bugzilla – Bug 479162
crash in Tasks:
Last modified: 2007-09-23 13:36:48 UTC
What were you doing when the application crashed? 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 109821952 vsize: 109821952 resident: 27230208 share: 17428480 rss: 27230208 rss_rlim: 4294967295 CPU usage: start_time: 1190397905 rtime: 1564 utime: 1196 stime: 368 cutime:55 cstime: 20 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 -1208375584 (LWP 3540)] [New Thread -1331151984 (LWP 26678)] [New Thread -1267139696 (LWP 26674)] [New Thread -1278022768 (LWP 3595)] [New Thread -1217127536 (LWP 3562)] (no debugging symbols found) 0x00f28402 in __kernel_vsyscall ()
+ Trace 164567
Thread 3 (Thread -1267139696 (LWP 26674))
----------- .xsession-errors (8 sec old) --------------------- 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 warning: .dynamic section for "/usr/lib/libaspell.so.15" is not at the expected address (wrong library or version mismatch?) 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 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 ***