GNOME Bugzilla – Bug 451060
crash in Tasks: clicking
Last modified: 2007-06-26 17:12:23 UTC
What were you doing when the application crashed? clicking 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.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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 161484800 vsize: 161484800 resident: 38567936 share: 22016000 rss: 38567936 rss_rlim: 4294967295 CPU usage: start_time: 1182813412 rtime: 1246 utime: 1178 stime: 68 cutime:44 cstime: 9 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 -1208232224 (LWP 5800)] [New Thread -1224832112 (LWP 10913)] [New Thread -1245811824 (LWP 5819)] [New Thread -1256301680 (LWP 5816)] [New Thread -1266791536 (LWP 5809)] (no debugging symbols found) 0x00999402 in __kernel_vsyscall ()
+ Trace 143694
Thread 1 (Thread -1208232224 (LWP 5800))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libbz2.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libaspell.so.15" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libstdc++.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libgcc_s.so.1" 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 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 436085 ***