GNOME Bugzilla – Bug 497064
crash in Home Folder:
Last modified: 2007-11-15 15:07:53 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Fedora Memory status: size: 98934784 vsize: 98934784 resident: 32382976 share: 16289792 rss: 32382976 rss_rlim: 4294967295 CPU usage: start_time: 1195137449 rtime: 165 utime: 60 stime: 105 cutime:0 cstime: 3 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 -1209022752 (LWP 3245)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 177885
Thread 1 (Thread -1209022752 (LWP 3245))
----------- .xsession-errors --------------------- /usr/lib/python2.5/site-packages/pirut/Progress.py:86: GtkWarning: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed self.pbar.set_fraction(fract) ** 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... warning: .dynamic section for "/usr/lib/libgnome-desktop-2.so.2" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib/libselinux.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations Initializing nautilus-open-terminal extension ** 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 ***