GNOME Bugzilla – Bug 466992
crash in Tasks:
Last modified: 2007-08-19 01:54:11 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 125800448 vsize: 125800448 resident: 45338624 share: 32935936 rss: 45338624 rss_rlim: 4294967295 CPU usage: start_time: 1185374775 rtime: 324 utime: 297 stime: 27 cutime:3 cstime: 6 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 -1208756512 (LWP 3274)] [New Thread -1281373296 (LWP 3775)] [New Thread -1260393584 (LWP 3302)] (no debugging symbols found) 0x004a0402 in __kernel_vsyscall ()
+ Trace 155426
Thread 1 (Thread -1208756512 (LWP 3274))
----------- .xsession-errors --------------------- warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libebook-1.2.so.9" 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/libedataserver-1.2.so.9" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libXi.so.6" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 431459 ***