GNOME Bugzilla – Bug 497862
crash in Open Folder: 1. open a folder on desk...
Last modified: 2007-11-20 19:46:17 UTC
Version: 2.18.3 What were you doing when the application crashed? 1. open a folder on desktop 2. click at my home folder 3. crash every folder change is a crash Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.18.3 2007-09-26 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-gentoo-r8 #1 Tue Oct 30 21:52:54 CET 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy P Icon Theme: osx Memory status: size: 256409600 vsize: 256409600 resident: 40349696 share: 20807680 rss: 40349696 rss_rlim: 18446744073709551615 CPU usage: start_time: 1195388923 rtime: 176 utime: 162 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal] (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) _______________________________________________________________________________ 0x00002afb73c48a1f in waitpid () from /lib/libpthread.so.0
+ Trace 178486
----------- .xsession-errors --------------------- ** Message: drive = 0 ** 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... Error while running hook_stop: Value can't be converted to integer. --------------------------------------------------
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 ***