GNOME Bugzilla – Bug 518186
crash in Open Folder: Anytime I open any of my...
Last modified: 2008-02-23 09:49:22 UTC
Version: 2.18.3 What were you doing when the application crashed? Anytime I open any of my Home folders the system crashes. Distribution: PCLinuxOS release 2007 (PCLinuxOS) for i586 Gnome Release: 2.18.0 2007-09-08 (%vendor) BugBuddy Version: 2.20.1 System: Linux 2.6.18.8.tex5 #1 SMP Thu May 10 11:36:58 WST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Wonderland Icon Theme: Neu Memory status: size: 80580608 vsize: 80580608 resident: 32960512 share: 18247680 rss: 32960512 rss_rlim: 4294967295 CPU usage: start_time: 1203736491 rtime: 361 utime: 330 stime: 31 cutime:2 cstime: 2 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/i686/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1228437824 (LWP 5604)] (no debugging symbols found) 0xb7f4b410 in __kernel_vsyscall ()
+ Trace 190162
Thread 1 (Thread -1228437824 (LWP 5604)): #-1 0xb7f4b410 in __kernel_vsyscall () No symbol table info available. ----------- .xsession-errors --------------------- Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Initializing gnome-mount 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... Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Initializing gnome-mount 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... Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded Backtrace limit of 200 exceeded --------------------------------------------------
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 ***