GNOME Bugzilla – Bug 534414
crash in File Browser: navegando entre carpetas...
Last modified: 2008-05-23 09:17:18 UTC
Version: 2.20.0 What were you doing when the application crashed? navegando entre carpetas de red 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 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: Glossy Icon Theme: gnome Memory status: size: 85078016 vsize: 85078016 resident: 27660288 share: 16879616 rss: 27660288 rss_rlim: 4294967295 CPU usage: start_time: 1211488088 rtime: 199 utime: 184 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 0xb6b88720 (LWP 2649)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198417
Thread 1 (Thread 0xb6b88720 (LWP 2649))
----------- .xsession-errors (10 sec old) --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ERROR: Couldn't attach to DCOP server! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! ERROR: Couldn't attach to DCOP server! ** (nautilus:2649): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «InFront»), avise a la lista de correo de gnome-vfs. ERROR: Couldn't attach to DCOP server! ERROR: Couldn't attach to DCOP server! --------------------------------------------------
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 ***