GNOME Bugzilla – Bug 450528
crash in Calendar: ??
Last modified: 2007-06-25 00:09:58 UTC
What were you doing when the application crashed? 更新 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 169050112 vsize: 169050112 resident: 49332224 share: 26640384 rss: 49332224 rss_rlim: 4294967295 CPU usage: start_time: 1182655125 rtime: 5694 utime: 5538 stime: 156 cutime:4840 cstime: 285 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 -1208375584 (LWP 28596)] [New Thread -1339614320 (LWP 14626)] [New Thread -1350104176 (LWP 14267)] [New Thread -1304953968 (LWP 28803)] [New Thread -1221076080 (LWP 28686)] (no debugging symbols found) 0x00d20402 in __kernel_vsyscall ()
+ Trace 143267
Thread 1 (Thread -1208375584 (LWP 28596))
----------- .xsession-errors (7 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 436128 ***