GNOME Bugzilla – Bug 554227
crash in File Browser: I just was coping files ...
Last modified: 2008-09-29 20:05:11 UTC
Version: 2.20.0 What were you doing when the application crashed? I just was coping files through the network Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-486 #1 Thu May 8 01:29:10 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 71360512 vsize: 71360512 resident: 33722368 share: 16605184 rss: 33722368 rss_rlim: 4294967295 CPU usage: start_time: 1222635863 rtime: 299 utime: 284 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 0xb6b4b720 (LWP 3565)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 207510
Thread 1 (Thread 0xb6b4b720 (LWP 3565))
----------- .xsession-errors (14 sec old) --------------------- (nautilus:3565): libgnomevfs-WARNING **: Failed to create service browser: Bad state (nautilus:3565): libgnomevfs-WARNING **: Failed to create service browser: Bad state (nautilus:3565): libgnomevfs-WARNING **: Failed to create service browser: Bad state (nautilus:3565): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running ** (nautilus:3565): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «pancho%202»), avise a la lista de correo de gnome-vfs. --------------------------------------------------
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 522534 ***