GNOME Bugzilla – Bug 490598
crash in Tasks: closing
Last modified: 2007-11-05 05:26:24 UTC
Version: 2.10 What were you doing when the application crashed? closing 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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 111050752 vsize: 111050752 resident: 37756928 share: 26890240 rss: 37756928 rss_rlim: 4294967295 CPU usage: start_time: 1193417291 rtime: 731 utime: 672 stime: 59 cutime:432 cstime: 37 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208355104 (LWP 4729)] [New Thread -1227883632 (LWP 11615)] [New Thread -1306379376 (LWP 4779)] [New Thread -1317262448 (LWP 4756)] (no debugging symbols found) 0x00639402 in __kernel_vsyscall ()
+ Trace 173092
Thread 2 (Thread -1227883632 (LWP 11615))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libgdk_pixbuf-2.0.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpng12.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpangocairo-1.0.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
Comment # 76 in bug 445309 (NOT GNOME) *** This bug has been marked as a duplicate of 445309 ***