GNOME Bugzilla – Bug 517232
crash in Open Folder: nothing
Last modified: 2008-02-18 15:43:36 UTC
Version: 2.18.1 What were you doing when the application crashed? nothing Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 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: 88326144 vsize: 88326144 resident: 33411072 share: 18038784 rss: 33411072 rss_rlim: 4294967295 CPU usage: start_time: 1203346727 rtime: 262 utime: 248 stime: 14 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 -1208650016 (LWP 3727)] (no debugging symbols found) 0x00588402 in __kernel_vsyscall ()
+ Trace 189608
Thread 1 (Thread -1208650016 (LWP 3727))
----------- .xsession-errors --------------------- localuser:divang being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3485 ** 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... ** 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... ** 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 ***