GNOME Bugzilla – Bug 480955
crash in Tasks: opening a photo attachme...
Last modified: 2007-09-29 01:39:21 UTC
Version: 2.10 What were you doing when the application crashed? opening a photo attachment 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 156852224 vsize: 156852224 resident: 60407808 share: 38109184 rss: 60407808 rss_rlim: 4294967295 CPU usage: start_time: 1190744245 rtime: 3829 utime: 3521 stime: 308 cutime:1 cstime: 2 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 -1208690976 (LWP 4051)] [New Thread -1280427120 (LWP 7515)] [New Thread -1224111216 (LWP 4153)] [New Thread -1344754800 (LWP 4119)] [New Thread -1334264944 (LWP 4118)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 165919
Thread 1 (Thread -1208690976 (LWP 4051))
----------- .xsession-errors --------------------- 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 warning: .dynamic section for "/usr/lib/libgsf-1.so.114" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations 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 --------------------------------------------------
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 467763 ***