GNOME Bugzilla – Bug 508015
crash in Open Folder: Opening a folder from th...
Last modified: 2008-01-08 09:32:19 UTC
Version: 2.18.3 What were you doing when the application crashed? Opening a folder from the File Browser Distribution: Fedora release 8 (Werewolf) 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 81657856 vsize: 81657856 resident: 25919488 share: 18034688 rss: 25919488 rss_rlim: 4294967295 CPU usage: start_time: 1199784347 rtime: 212 utime: 192 stime: 20 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) [Thread debugging using libthread_db enabled] [New Thread -1208703264 (LWP 10457)] [New Thread -1233126512 (LWP 10475)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184492
Thread 1 (Thread -1208703264 (LWP 10457))
----------- .xsession-errors --------------------- warning: .dynamic section for "/lib/libgcc_s.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations 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 --- Hash table keys for warning below: --> file:///home/rrodriguez (nautilus:10470): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers)) aborting... --------------------------------------------------
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 459221 ***