GNOME Bugzilla – Bug 552020
crash in File Browser:
Last modified: 2008-09-13 09:44:57 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-486 #1 Thu May 8 01:29:10 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Aero-ion3.1 Icon Theme: Nuvola Memory status: size: 78082048 vsize: 78082048 resident: 32460800 share: 16887808 rss: 32460800 rss_rlim: 4294967295 CPU usage: start_time: 1221269575 rtime: 784 utime: 739 stime: 45 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 0xb6bf8720 (LWP 7395)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 206699
Thread 1 (Thread 0xb6bf8720 (LWP 7395))
----------- .xsession-errors --------------------- Initializing gnome-mount extension ** (nm-applet:4418): WARNING **: <WARN> nmi_dbus_get_network_properties(): applet-dbus-info.c:406 - couldn't retrieve security information from GConf for 'Sibuls-disconec'. No se puede abrir el archivo de escritorio /home/rodrigo/Desktop/xchat.desktop para el lanzador del panel: No existe el fichero o el directorio connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:4397): 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. seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:7395): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Mi%20m%C3%BAsica»), 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 ***