GNOME Bugzilla – Bug 429749
crash in Tasks: closing evo
Last modified: 2007-04-15 19:51:23 UTC
What were you doing when the application crashed? closing evo Distribution: Fedora release 6.92 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-0.30.rc6.mm1.fc7 #1 SMP Mon Apr 9 05:47:40 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 655945728 vsize: 655945728 resident: 49618944 share: 18853888 rss: 49618944 rss_rlim: 18446744073709551615 CPU usage: start_time: 1176569092 rtime: 1356 utime: 1204 stime: 152 cutime:2 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47080558492592 (LWP 9014)] 0x000000359aa0d83f in __libc_waitpid (pid=13231, stat_loc=0x7fffdeb6d97c, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 127778
Thread 1 (Thread 47080558492592 (LWP 9014))
----------- .xsession-errors (35 sec old) --------------------- warning: .dynamic section for "/usr/lib64/evolution/2.10/libevolution-a11y.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/evolution/2.10/libeutil.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib64/libdbus-1.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libpanel-applet-2.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib64/evolution/2.10/components/libevolution-mail.so" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 334966 ***