GNOME Bugzilla – Bug 455130
crash in Tasks: Closing evolution
Last modified: 2007-10-05 09:59:07 UTC
What were you doing when the application crashed? Closing evolution Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 166084608 vsize: 166084608 resident: 47095808 share: 23359488 rss: 47095808 rss_rlim: 4294967295 CPU usage: start_time: 1183968027 rtime: 2231 utime: 2113 stime: 118 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208580384 (LWP 5807)] [New Thread -1304695920 (LWP 5992)] [New Thread -1235293296 (LWP 5953)] (no debugging symbols found) 0x00fd3402 in __kernel_vsyscall ()
+ Trace 146703
Thread 1 (Thread -1208580384 (LWP 5807))
----------- .xsession-errors (9 sec old) --------------------- warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/evolution/2.10/libevolution-widgets-a11y.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/evolution/2.10/libevolution-a11y.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/evolution/2.10/libeutil.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/evolution/2.10/components/libevolution-mail.so" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 477793 ***