GNOME Bugzilla – Bug 460228
crash in Open Folder: all i did was double cli...
Last modified: 2007-07-26 13:05:03 UTC
Version: 2.19.5 What were you doing when the application crashed? all i did was double click on a directory on my desktop! Distribution: Fedora release 7.89 (Rawhide) Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23-0.45.rc0.git16.fc8 #1 SMP Mon Jul 23 09:35:47 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 89849856 vsize: 89849856 resident: 36601856 share: 22507520 rss: 36601856 rss_rlim: 4294967295 CPU usage: start_time: 1185353975 rtime: 494 utime: 392 stime: 102 cutime:17 cstime: 7 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 -1208731888 (LWP 3070)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 150437
Thread 1 (Thread -1208731888 (LWP 3070))
----------- .xsession-errors (12 sec old) --------------------- package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Max failures exceeded, exiting now PARSING /usr/share/poppler/nameToUnicode/Thai PARSING /usr/share/poppler/nameToUnicode/Bulgarian PARSING /usr/share/poppler/nameToUnicode/Thai PARSING /usr/share/poppler/nameToUnicode/Bulgarian PARSING /usr/share/poppler/nameToUnicode/Thai PARSING /usr/share/poppler/nameToUnicode/Bulgarian ** 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... --------------------------------------------------
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 ***