GNOME Bugzilla – Bug 538685
crash in File Browser: connect to a pc via net
Last modified: 2008-06-17 07:50:24 UTC
Version: 2.20.0 What were you doing when the application crashed? connect to a pc via net Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: LeopardX Memory status: size: 98988032 vsize: 98988032 resident: 28659712 share: 17559552 rss: 28659712 rss_rlim: 4294967295 CPU usage: start_time: 1213659935 rtime: 190 utime: 174 stime: 16 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 0xb6bb0720 (LWP 12650)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200607
Thread 1 (Thread 0xb6bb0720 (LWP 12650))
----------- .xsession-errors --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3364): WARNING **: Hit unhandled case 31 (La operación ha sido cancelada) in fm_report_error_loading_directory connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:12650): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Documentos%20c»), 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 ***