GNOME Bugzilla – Bug 510457
crash in Open Folder: Distribution: Fedora rel...
Last modified: 2008-01-19 01:20:35 UTC
Version: 2.19.5 What were you doing when the application crashed? 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: Enforcing Accessibility: Enabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 477868032 vsize: 477868032 resident: 40951808 share: 23449600 rss: 40951808 rss_rlim: 18446744073709551615 CPU usage: start_time: 1200720636 rtime: 403 utime: 300 stime: 103 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 3093)] [New Thread 1105209680 (LWP 3317)] (no debugging symbols found) 0x00002aaab0b0697f in waitpid () from /lib64/libpthread.so.0
+ Trace 185862
Thread 1 (Thread 46912700132112 (LWP 3093))
----------- .xsession-errors --------------------- console-kit-daemon (pid 2290) is running... ConsoleKit console-kit-daemon (pid 2290) is running... ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ConsoleKit console-kit-daemon (pid 2290) is running... ConsoleKit console-kit-daemon (pid 2290) is running... ConsoleKit console-kit-daemon (pid 2290) is running... ** 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 0x7fff59bfc000 --------------------------------------------------
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 ***