GNOME Bugzilla – Bug 487433
crash in Open Folder: I have installed a wirel...
Last modified: 2007-10-19 01:46:28 UTC
Version: 2.18.3 What were you doing when the application crashed? I have installed a wireless adapter (WPN311) using madwifi. I was trying to access my personal folders Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 67960832 vsize: 67960832 resident: 30646272 share: 17833984 rss: 30646272 rss_rlim: 4294967295 CPU usage: start_time: 1192611690 rtime: 235 utime: 211 stime: 24 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 -1208596768 (LWP 5121)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170789
Thread 1 (Thread -1208596768 (LWP 5121))
----------- .xsession-errors (7 sec old) --------------------- localuser:98cwitr being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/4893 ** 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... ConsoleKit console-kit-daemon (pid 2172) is running... ConsoleKit console-kit-daemon (pid 2172) is running... ConsoleKit console-kit-daemon (pid 2172) is running... ** 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 ***