GNOME Bugzilla – Bug 508814
crash in Open Folder:
Last modified: 2008-01-12 11:30:13 UTC
Version: 2.18.3 What were you doing when the application crashed? 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.22.10.tex1 #1 SMP Thu Oct 11 09:44:19 WST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Ro_Dream Memory status: size: 91766784 vsize: 91766784 resident: 41418752 share: 23433216 rss: 41418752 rss_rlim: 4294967295 CPU usage: start_time: 1200072690 rtime: 510 utime: 464 stime: 46 cutime:1 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 -1228679488 (LWP 5921)] (no debugging symbols found) 0xb7f17410 in __kernel_vsyscall ()
+ Trace 184962
Thread 1 (Thread -1228679488 (LWP 5921)): #-1 0xb7f17410 in __kernel_vsyscall () No symbol table info available. ----------- .xsession-errors --------------------- (synaptic:5946): Gtk-CRITICAL **: gtk_label_set_label: assertion `GTK_IS_LABEL (label)' failed (synaptic:5946): Gtk-CRITICAL **: gtk_label_set_label: assertion `GTK_IS_LABEL (label)' failed (synaptic:5946): Gtk-CRITICAL **: gtk_label_set_label: assertion `GTK_IS_LABEL (label)' failed (synaptic:5946): Gtk-CRITICAL **: gtk_label_set_label: assertion `GTK_IS_LABEL (label)' failed Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 ** 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 ***