GNOME Bugzilla – Bug 485650
crash in Open Folder: was displaying the compu...
Last modified: 2007-10-13 00:16:08 UTC
Version: 2.18.3 What were you doing when the application crashed? was displaying the computer properly 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: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 86089728 vsize: 86089728 resident: 24915968 share: 17698816 rss: 24915968 rss_rlim: 4294967295 CPU usage: start_time: 1192091078 rtime: 87 utime: 82 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) [Thread debugging using libthread_db enabled] [New Thread -1209026848 (LWP 3496)] [New Thread -1234179184 (LWP 3511)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169440
Thread 1 (Thread -1209026848 (LWP 3496))
----------- .xsession-errors --------------------- --> file:///home/smrithi (nautilus:3466): 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... Initializing nautilus-open-terminal extension --- Hash table keys for warning below: --> file:///home/smrithi (nautilus:3505): 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 ***