GNOME Bugzilla – Bug 465298
crash in Email:
Last modified: 2007-08-22 20:54:58 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 207802368 vsize: 207802368 resident: 94203904 share: 48435200 rss: 94203904 rss_rlim: 4294967295 CPU usage: start_time: 1186709309 rtime: 12392 utime: 11030 stime: 1362 cutime:162 cstime: 103 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 -1208232224 (LWP 2905)] [New Thread -1223259248 (LWP 3833)] [New Thread -1332237424 (LWP 2981)] [New Thread -1266693232 (LWP 2947)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 154151
Thread 1 (Thread -1208232224 (LWP 2905))
----------- .xsession-errors (8 sec old) --------------------- warning: .dynamic section for "/usr/lib/librsvg-2.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgsf-1.so.114" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" 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 taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 426807 ***