GNOME Bugzilla – Bug 536494
crash in File Browser: navegando mi red de 10 p...
Last modified: 2008-06-03 22:21:55 UTC
Version: 2.20.0 What were you doing when the application crashed? navegando mi red de 10 pc Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 94502912 vsize: 94502912 resident: 25980928 share: 14266368 rss: 25980928 rss_rlim: 4294967295 CPU usage: start_time: 1212515039 rtime: 5325 utime: 4942 stime: 383 cutime:0 cstime: 4 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b81720 (LWP 2942)] (no debugging symbols found) 0xb75c0f91 in waitpid () from /lib/libpthread.so.0
+ Trace 199515
Thread 1 (Thread 0xb6b81720 (LWP 2942))
----------- .xsession-errors (202 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:2942): 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. ** (x-session-manager:2856): WARNING **: Host name lookup failure on localhost. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-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 ***