GNOME Bugzilla – Bug 530463
crash in File Browser:
Last modified: 2008-04-29 07:16:22 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Gorilla Memory status: size: 81940480 vsize: 81940480 resident: 26763264 share: 16789504 rss: 26763264 rss_rlim: 4294967295 CPU usage: start_time: 1209427123 rtime: 223 utime: 214 stime: 9 cutime:2 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 0xb6b78720 (LWP 26772)] [New Thread 0xb56a3b90 (LWP 26810)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196381
Thread 1 (Thread 0xb6b78720 (LWP 26772))
----------- .xsession-errors --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:26772): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Documents»), avise a la lista de correo de gnome-vfs. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! --------------------------------------------------
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 ***