GNOME Bugzilla – Bug 509213
crash in Open Folder: searching for files accr...
Last modified: 2008-01-13 23:22:36 UTC
Version: 2.18.3 What were you doing when the application crashed? searching for files accross two disks Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 90275840 vsize: 90275840 resident: 24891392 share: 15683584 rss: 24891392 rss_rlim: 4294967295 CPU usage: start_time: 1200251793 rtime: 4075 utime: 3621 stime: 454 cutime:250 cstime: 64 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 -1208744224 (LWP 2800)] [New Thread -1273783408 (LWP 5978)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 185196
Thread 2 (Thread -1273783408 (LWP 5978))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libgstaudio-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgnome-window-settings.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpanel-applet-2.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 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 454799 ***