GNOME Bugzilla – Bug 520396
crash in Tasks: exiting
Last modified: 2008-03-04 23:09:02 UTC
Version: 2.10 What were you doing when the application crashed? exiting 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: Crux Icon Theme: Crux Memory status: size: 111206400 vsize: 111206400 resident: 36425728 share: 25714688 rss: 36425728 rss_rlim: 4294967295 CPU usage: start_time: 1204636054 rtime: 1653 utime: 1519 stime: 134 cutime:0 cstime: 1 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 -1209137440 (LWP 2496)] [New Thread -1314940016 (LWP 23448)] [New Thread -1251263600 (LWP 2557)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191313
Thread 2 (Thread -1314940016 (LWP 23448))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libgnome-2.so.0" 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 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 445309 ***