GNOME Bugzilla – Bug 525686
crash in Open Folder:
Last modified: 2008-04-04 10:25:49 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 78995456 vsize: 78995456 resident: 28971008 share: 17301504 rss: 28971008 rss_rlim: 4294967295 CPU usage: start_time: 1207105212 rtime: 228 utime: 213 stime: 15 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b93720 (LWP 4552)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 193966
Thread 1 (Thread 0xb6b93720 (LWP 4552))
----------- .xsession-errors --------------------- kbuildsycoca running... Reusing existing ksycoca ICE default IO error handler doing an exit(), pid = 4363, errno = 0 Initializing gnome-mount extension Initializing nautilus-open-terminal extension seahorse nautilus module initialized ** (nautilus:4502): WARNING **: No description found for mime type "x-directory/smb-share" (file is "change(max)"), please tell the gnome-vfs mailing list. Initializing gnome-mount extension Initializing nautilus-open-terminal extension seahorse nautilus module initialized (synaptic:4586): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed ** (nautilus:4552): WARNING **: No description found for mime type "x-directory/smb-share" (file is "My%20Documents"), please tell the gnome-vfs mailing list. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 525181 ***