GNOME Bugzilla – Bug 536890
crash in File Browser:
Last modified: 2008-06-06 12:37:53 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-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: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 86130688 vsize: 86130688 resident: 31662080 share: 16437248 rss: 31662080 rss_rlim: 4294967295 CPU usage: start_time: 1212683728 rtime: 170 utime: 164 stime: 6 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 0xb6c07720 (LWP 4271)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199681
Thread 1 (Thread 0xb6c07720 (LWP 4271))
----------- .xsession-errors --------------------- connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3222): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «www»), avise a la lista de correo de gnome-vfs. /home/juan/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style' Initializing gnome-mount extension seahorse nautilus module initialized /home/juan/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style' ** (nautilus:4271): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «www»), avise a la lista de correo de gnome-vfs. /home/juan/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style' --------------------------------------------------
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 ***