GNOME Bugzilla – Bug 517595
crash in Open Folder:
Last modified: 2008-02-20 10:46:39 UTC
Version: 2.18.3 What were you doing when the application crashed? 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 64757760 vsize: 64757760 resident: 26873856 share: 15114240 rss: 26873856 rss_rlim: 4294967295 CPU usage: start_time: 1203476809 rtime: 123 utime: 115 stime: 8 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 -1208359200 (LWP 5500)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 189816
Thread 1 (Thread -1208359200 (LWP 5500))
----------- .xsession-errors --------------------- You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. Traceback (most recent call last): File "/usr/share/system-config-printer/applet.py", line 20, in ? import cups ImportError: No module named cups ** 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... ** 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 ***