GNOME Bugzilla – Bug 461132
crash in Calendar: ?
Last modified: 2007-07-28 13:21:57 UTC
Version: 2.10 What were you doing when the application crashed? ? 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-27.fc7 #1 SMP Tue Jul 17 17:13:26 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: 165027840 vsize: 165027840 resident: 63643648 share: 40280064 rss: 63643648 rss_rlim: 4294967295 CPU usage: start_time: 1185581302 rtime: 1865 utime: 1756 stime: 109 cutime:2 cstime: 4 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 -1208330528 (LWP 3325)] [New Thread -1326883952 (LWP 15265)] [New Thread -1263944816 (LWP 3411)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 151092
Thread 1 (Thread -1208330528 (LWP 3325))
----------- .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 444852 ***