GNOME Bugzilla – Bug 534097
crash in File Browser:
Last modified: 2008-05-20 23:16:29 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 Sat Apr 19 00:37:55 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: 65437696 vsize: 65437696 resident: 27762688 share: 16543744 rss: 27762688 rss_rlim: 4294967295 CPU usage: start_time: 1211313032 rtime: 323 utime: 307 stime: 16 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 0xb6bf4720 (LWP 3088)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198256
Thread 1 (Thread 0xb6bf4720 (LWP 3088))
----------- .xsession-errors --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:3088): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «Gretag»), 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 ***