GNOME Bugzilla – Bug 471135
crash in Tasks: changing my signature
Last modified: 2007-09-21 18:51:49 UTC
Version: 2.10 What were you doing when the application crashed? changing my signature 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 232710144 vsize: 232710144 resident: 92831744 share: 55971840 rss: 92831744 rss_rlim: 4294967295 CPU usage: start_time: 1187979221 rtime: 10517 utime: 9680 stime: 837 cutime:2 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208650016 (LWP 975)] [New Thread -1210750064 (LWP 1483)] [New Thread -1334850672 (LWP 1091)] [New Thread -1262232688 (LWP 1046)] [New Thread -1221239920 (LWP 1045)] 0x00110402 in __kernel_vsyscall ()
+ Trace 158527
Thread 1 (Thread -1208650016 (LWP 975))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libldap-2.3.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libedata-book-1.2.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libedata-cal-1.2.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/librsvg-2.so.2" 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 433573 ***