GNOME Bugzilla – Bug 491841
crash in Tasks:
Last modified: 2007-10-31 21:48:18 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 116723712 vsize: 116723712 resident: 41934848 share: 34308096 rss: 41934848 rss_rlim: 4294967295 CPU usage: start_time: 1193770202 rtime: 243 utime: 207 stime: 36 cutime:0 cstime: 1 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 -1208428832 (LWP 3606)] [New Thread -1257997424 (LWP 32376)] [New Thread -1228932208 (LWP 3660)] (no debugging symbols found) 0x00110402 in ?? () from /lib/libcrypto.so.6
+ Trace 173997
Thread 1 (Thread -1208428832 (LWP 3606))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libpangoft2-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/libpng12.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libpangocairo-1.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libpango-1.0.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libssl.so.6" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib/libcrypto.so.6" 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 we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 364700 ***