GNOME Bugzilla – Bug 470925
crash in Open Folder: just started nautilus an...
Last modified: 2007-09-03 14:48:52 UTC
Version: 2.19.5 What were you doing when the application crashed? just started nautilus and selected up one level Distribution: Fedora release 7.90 (Rawhide) Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23-0.61.rc1.git9.fc8 #1 SMP Tue Jul 31 17:14:25 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 469417984 vsize: 469417984 resident: 35450880 share: 17670144 rss: 35450880 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188279226 rtime: 316 utime: 214 stime: 102 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912700132112 (LWP 2659)] (no debugging symbols found) 0x00002aaab0b0697f in waitpid () from /lib64/libpthread.so.0
+ Trace 158358
Thread 1 (Thread 46912700132112 (LWP 2659))
----------- .xsession-errors --------------------- Local variables in innermost frame: highdict: {} self: <yum.packageSack.ListPackageSack object at 0x7475e50> naTup: ('glibc', 'i686') where: None compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 gtk-window-decorator: Could not acquire decoration manager selection on screen 0 display ":0.0" ** ERROR **: file nautilus-navigation-window.c: line 823 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers)) aborting... warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff533e5000 --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 465410 ***