GNOME Bugzilla – Bug 520023
crash in Tasks: Opened an e-mail message...
Last modified: 2008-03-06 13:43:14 UTC
Version: 2.10 What were you doing when the application crashed? Opened an e-mail message. 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 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Gnomeproject-0.1 Memory status: size: 335241216 vsize: 335241216 resident: 230174720 share: 50827264 rss: 230174720 rss_rlim: 4294967295 CPU usage: start_time: 1204485168 rtime: 13414 utime: 11967 stime: 1447 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208879392 (LWP 3618)] [New Thread -1241179248 (LWP 3709)] [New Thread -1286325360 (LWP 3701)] [New Thread -1262158960 (LWP 3643)] 0x00110402 in __kernel_vsyscall ()
+ Trace 191111
Thread 1 (Thread -1208879392 (LWP 3618))
----------- .xsession-errors (26 sec old) --------------------- warning: .dynamic section for "/usr/lib/libnm_glib.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libdbus-1.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libavahi-client.so.3" 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 458670 ***