GNOME Bugzilla – Bug 485861
crash in File Browser:
Last modified: 2007-10-13 00:18:02 UTC
Version: 2.18.3 What were you doing when the application crashed? 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-Breathe Icon Theme: yasis Memory status: size: 86167552 vsize: 86167552 resident: 30203904 share: 18259968 rss: 30203904 rss_rlim: 4294967295 CPU usage: start_time: 1192136968 rtime: 397 utime: 350 stime: 47 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 -1208432928 (LWP 2431)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169603
Thread 1 (Thread -1208432928 (LWP 2431))
----------- .xsession-errors (6 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** 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... /usr/share/themes/Clearlooks-Breathe/gtk-2.0/gtkrc:50: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /usr/share/themes/Clearlooks-Breathe/gtk-2.0/gtkrc:51: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /usr/share/themes/Clearlooks-Breathe/gtk-2.0/gtkrc:52: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. --------------------------------------------------
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 ***