GNOME Bugzilla – Bug 483528
crash in Open Folder: Opening a directory that...
Last modified: 2007-10-10 23:07:32 UTC
Version: 2.18.3 What were you doing when the application crashed? Opening a directory that has camera files in it via mass usb storage. I dont know why it does this now consistently. It used to work fine. I can access the directory fine if i use command line. Distribution: Unknown Gnome Release: 2.18.3 2007-07-07 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.22-ARCH #1 SMP PREEMPT Wed Sep 26 20:57:40 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 72216576 vsize: 72216576 resident: 20873216 share: 14020608 rss: 20873216 rss_rlim: 4294967295 CPU usage: start_time: 1191540066 rtime: 237 utime: 224 stime: 13 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 -1227536704 (LWP 9245)] 0xb7f9f410 in __kernel_vsyscall ()
+ Trace 167834
Thread 1 (Thread -1227536704 (LWP 9245))
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 ** 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... Initializing gnome-mount extension ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** 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 ***