GNOME Bugzilla – Bug 518865
crash in Tasks: Closing Preferences dial...
Last modified: 2008-02-28 07:44:16 UTC
Version: 2.10 What were you doing when the application crashed? Closing Preferences dialog. 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 209121280 vsize: 209121280 resident: 103485440 share: 44912640 rss: 103485440 rss_rlim: 4294967295 CPU usage: start_time: 1203954446 rtime: 24066 utime: 22654 stime: 1412 cutime:311 cstime: 85 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 -1208629536 (LWP 8549)] [New Thread -1307575408 (LWP 25969)] [New Thread -1301701744 (LWP 8890)] [New Thread -1228215408 (LWP 8609)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190515
Thread 1 (Thread -1208629536 (LWP 8549))
----------- .xsession-errors (10 sec old) --------------------- warning: .dynamic section for "/usr/lib/libkrb5support.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libldap-2.3.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/liblber-2.3.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations 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 --------------------------------------------------
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 447591 ***