GNOME Bugzilla – Bug 466284
crash in Open Folder: Clicked the up button to...
Last modified: 2007-09-03 14:43:53 UTC
Version: 2.19.5 What were you doing when the application crashed? Clicked the up button to go up a directory level. Distribution: Fedora release 7.90 (Rawhide) Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23-0.61.rc1.git9.fc8 #1 SMP Tue Jul 31 17:23:22 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 85618688 vsize: 85618688 resident: 34091008 share: 20869120 rss: 34091008 rss_rlim: 4294967295 CPU usage: start_time: 1187022213 rtime: 225 utime: 196 stime: 29 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) 0x0012d402 in __kernel_vsyscall ()
+ Trace 154898
----------- .xsession-errors --------------------- warning: .dynamic section for "/lib/libc.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations ** ERROR **: file nautilus-navigation-window.c: line 823 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers)) aborting... warning: .dynamic section for "/usr/lib/libgnome-keyring.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgdk-x11-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgdk_pixbuf-2.0.so.0" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/gtk-2.0/modules/libgail.so" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 465410 ***