GNOME Bugzilla – Bug 548458
crash in File Browser: browsing a shared folder...
Last modified: 2008-08-19 17:05:34 UTC
Version: 2.20.0 What were you doing when the application crashed? browsing a shared folder in a Windows XP machine Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (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: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Yattacier3 Icon Theme: Amaranth Memory status: size: 90935296 vsize: 90935296 resident: 32067584 share: 17530880 rss: 32067584 rss_rlim: 4294967295 CPU usage: start_time: 1219155635 rtime: 163 utime: 154 stime: 9 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 0xb6b7d710 (LWP 3963)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 205352
Thread 1 (Thread 0xb6b7d710 (LWP 3963))
----------- .xsession-errors --------------------- ** (nautilus:3104): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «C%24»), avise a la lista de correo de gnome-vfs. Input File : '/usr/share/amsn/skins/default/sounds/online.wav' Sample Size : 16-bit (2 bytes) Sample Encoding: signed (2's complement) Channels : 2 Sample Rate : 44100 Time: 00:00.00 [00:00.81] of 00:00.81 (0.00%) Samples out: 0 Clips: 0 Time: 00:00.37 [00:00.44] of 00:00.81 (45.6%) Samples out: 17.4k Clips: 0 Time: 00:00.56 [00:00.26] of 00:00.81 (68.4 Done. Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:3963): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «C%24»), 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 ***