GNOME Bugzilla – Bug 498133
crash in Open Folder: opening a directory on a...
Last modified: 2007-11-20 19:46:50 UTC
Version: 2.18.3 What were you doing when the application crashed? opening a directory on a external hardrive (ntfs) Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-11-04 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.21-suspend2-r7 #1 SMP PREEMPT Mon Aug 27 23:44:42 WST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 79949824 vsize: 79949824 resident: 23674880 share: 14606336 rss: 23674880 rss_rlim: 40960000 CPU usage: start_time: 1195465406 rtime: 170 utime: 165 stime: 5 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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 178669
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** 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... --------------------------------------------------
Further information Crash occurs when opening directories in browse mode and is not limited to external drive. Crash does not occur when opening a folder to a new window.
I rebuilt nautilus with debugging symbols to get a better trace but can't reproduce the problem with the new binary...
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 ***