GNOME Bugzilla – Bug 473525
crash in Tasks: Shutting down Evolution ...
Last modified: 2007-09-17 10:44:13 UTC
What were you doing when the application crashed? Shutting down Evolution after setting preferences 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 128618496 vsize: 128618496 resident: 36990976 share: 21143552 rss: 36990976 rss_rlim: 4294967295 CPU usage: start_time: 1188902734 rtime: 2151 utime: 1708 stime: 443 cutime:81 cstime: 88 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208977696 (LWP 19177)] [New Thread -1249559664 (LWP 21001)] [New Thread -1313072240 (LWP 20895)] (no debugging symbols found) 0x00a05402 in __kernel_vsyscall ()
+ Trace 160356
Thread 1 (Thread -1208977696 (LWP 19177))
----------- .xsession-errors (21 sec old) --------------------- warning: .dynamic section for "/usr/lib/evolution/2.10/libeshell.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/libetimezonedialog.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libecal-1.2.so.7" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations 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 --------------------------------------------------
*** This bug has been marked as a duplicate of 426227 ***