GNOME Bugzilla – Bug 538726
crash in File Browser: I was browsing folders
Last modified: 2008-06-17 17:54:24 UTC
Version: 2.20.0 What were you doing when the application crashed? I was browsing folders 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: Clearlooks Icon Theme: gnome Memory status: size: 89645056 vsize: 89645056 resident: 35168256 share: 16711680 rss: 35168256 rss_rlim: 4294967295 CPU usage: start_time: 1213689095 rtime: 273 utime: 255 stime: 18 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 0xb6b60720 (LWP 6476)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200631
Thread 1 (Thread 0xb6b60720 (LWP 6476))
----------- .xsession-errors --------------------- CALLBACK: fill-authentication!!! ** (nautilus:3309): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «htdocs»), avise a la lista de correo de gnome-vfs. warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations Initializing gnome-mount extension seahorse nautilus module initialized connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:6476): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «htdocs»), 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 ***