GNOME Bugzilla – Bug 453052
crash in Open Folder: closed nautilus.
Last modified: 2007-07-02 20:45:49 UTC
Version: 2.18.1 What were you doing when the application crashed? closed nautilus. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 102006784 vsize: 102006784 resident: 39104512 share: 25718784 rss: 39104512 rss_rlim: 4294967295 CPU usage: start_time: 1183363883 rtime: 5292 utime: 4629 stime: 663 cutime:216 cstime: 169 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 -1208514848 (LWP 2477)] [New Thread -1230402672 (LWP 8405)] (no debugging symbols found) 0x00789402 in __kernel_vsyscall ()
+ Trace 145213
Thread 1 (Thread -1208514848 (LWP 2477))
----------- .xsession-errors (7 sec old) --------------------- warning: .dynamic section for "/usr/lib/libhal.so.1" 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/libmetacity-private.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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 416114 ***