GNOME Bugzilla – Bug 461363
crash in Tasks: Looking at preferences.
Last modified: 2007-07-29 15:57:56 UTC
Version: 2.10 What were you doing when the application crashed? Looking at preferences. 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.22.1-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 192999424 vsize: 192999424 resident: 108621824 share: 43229184 rss: 108621824 rss_rlim: 4294967295 CPU usage: start_time: 1185659101 rtime: 4656 utime: 3719 stime: 937 cutime:2 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 -1208969504 (LWP 3570)] [New Thread -1251812464 (LWP 17630)] [New Thread -1300247664 (LWP 3664)] [New Thread -1241322608 (LWP 3614)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 151268
Thread 1 (Thread -1208969504 (LWP 3570))
----------- .xsession-errors (8 sec old) --------------------- warning: .dynamic section for "/lib/libattr.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libacl.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libfam.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libbeagle.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 438139 ***