GNOME Bugzilla – Bug 519641
crash in Open Folder: Listing files in yum.rep...
Last modified: 2008-02-29 23:57:10 UTC
Version: 2.18.3 What were you doing when the application crashed? Listing files in yum.repos.d at the same time as I was running 'yum upgrade' Distribution: Fedora release 8 (Werewolf) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 106643456 vsize: 106643456 resident: 42106880 share: 18575360 rss: 42106880 rss_rlim: 4294967295 CPU usage: start_time: 1204323167 rtime: 319 utime: 294 stime: 25 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 -1208666352 (LWP 3144)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190896
Thread 1 (Thread -1208666352 (LWP 3144))
----------- .xsession-errors --------------------- SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/3018,unix/unix:/tmp/.ICE-unix/3018 Window manager warning: Failed to read saved session file /home/bpn01/.metacity/sessions/default1.ms: Failed to open file '/home/bpn01/.metacity/sessions/default1.ms': No such file or directory --- Hash table keys for warning below: --> file:///home/bpn01 (nautilus:3492): 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 ***