GNOME Bugzilla – Bug 444162
crash in Tasks: unplugged usb drive whil...
Last modified: 2007-06-05 22:45:11 UTC
What were you doing when the application crashed? unplugged usb drive while in drive mount Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 148066304 vsize: 148066304 resident: 50106368 share: 22417408 rss: 50106368 rss_rlim: 4294967295 CPU usage: start_time: 1180997439 rtime: 4471 utime: 4262 stime: 209 cutime:0 cstime: 0 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 -1208797472 (LWP 4746)] [New Thread -1293980784 (LWP 4766)] [New Thread -1240892528 (LWP 4757)] [New Thread -1230005360 (LWP 4752)] (no debugging symbols found) 0x00673402 in __kernel_vsyscall ()
+ Trace 138298
Thread 1 (Thread -1208797472 (LWP 4746))
----------- .xsession-errors --------------------- warning: .dynamic section for "/lib/libattr.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libacl.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libfam.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libbeagle.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 426807 ***