GNOME Bugzilla – Bug 543264
crash in File Browser: accediendo a una carpeta...
Last modified: 2008-07-16 12:30:31 UTC
Version: 2.20.0 What were you doing when the application crashed? accediendo a una carpeta compartida en windows server 2003 Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: SphereCrystal Memory status: size: 459276288 vsize: 459276288 resident: 32395264 share: 18075648 rss: 32395264 rss_rlim: 18446744073709551615 CPU usage: start_time: 1216150034 rtime: 194 utime: 172 stime: 22 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2ad068195b60 (LWP 3758)] (no debugging symbols found) 0x00002ad060d26edf in waitpid () from /lib/libpthread.so.0
+ Trace 202981
Thread 1 (Thread 0x2ad068195b60 (LWP 3758))
----------- .xsession-errors --------------------- (shares-admin:7036): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed (gnome-help:7193): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. (gnome-help:7193): Yelp-WARNING **: Cannot find dbus bus ** (nautilus:3758): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Download»), avise a la lista de correo de gnome-vfs. 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 ***