GNOME Bugzilla – Bug 475211
crash in Open Folder: Searching the hard disk ...
Last modified: 2007-12-21 02:59:56 UTC
Version: 2.18.3 What were you doing when the application crashed? Searching the hard disk (file system) for "doom" to find where the Doom 3 demo installed. 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: crystalsvg Memory status: size: 163520512 vsize: 163520512 resident: 49922048 share: 41771008 rss: 49922048 rss_rlim: 4294967295 CPU usage: start_time: 1189214425 rtime: 10238 utime: 8841 stime: 1397 cutime:975 cstime: 230 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 -1208301856 (LWP 2463)] [New Thread -1241871472 (LWP 31126)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 161598
Thread 2 (Thread -1241871472 (LWP 31126))
----------- .xsession-errors (8 sec old) --------------------- warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libcom_err.so.2" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libk5crypto.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libkrb5support.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 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
(Hi Andre, I installed the packages you asked me to install, and ran the search again. I got a little bit more output, I hope this is what you wanted. This is happening from inside the Nautilus file browser; I can go to the panel and click Places -> Search for Files and it works fine. I am pasting in the whole thing, data follows: 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: crystalsvg Memory status: size: 140890112 vsize: 140890112 resident: 46514176 share: 31301632 rss: 46514176 rss_rlim: 4294967295 CPU usage: start_time: 1189555938 rtime: 1672 utime: 1242 stime: 430 cutime:0 cstime: 0 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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208379680 (LWP 2482)] [New Thread -1314100336 (LWP 2897)] 0x00110402 in __kernel_vsyscall ()
+ Trace 162230
Thread 2 (Thread -1314100336 (LWP 2897))
----------- .xsession-errors (36 sec old) --------------------- warning: the debug information found in "/usr/lib/debug//usr/bin/nautilus.debug" does not match "/usr/bin/nautilus" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib/libnautilus-extension.so.1.1.0.debug" does not match "/usr/lib/libnautilus-extension.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so" (CRC misma warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so" (CRC mis warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so" (CRC misma --------------------------------------------------
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 ***