GNOME Bugzilla – Bug 532882
crash in File Browser: i was trying to access i...
Last modified: 2008-05-13 07:56:16 UTC
Version: 2.20.0 What were you doing when the application crashed? i was trying to access into a shared folder of my local network on windows and it's crash 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: 90046464 vsize: 90046464 resident: 34930688 share: 16609280 rss: 34930688 rss_rlim: 4294967295 CPU usage: start_time: 1210648481 rtime: 163 utime: 150 stime: 13 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 0xb6b99720 (LWP 13773)] [New Thread 0xb696cb90 (LWP 14305)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 197594
Thread 1 (Thread 0xb6b99720 (LWP 13773))
----------- .xsession-errors --------------------- sh: iwconfig: command not found sh: iwconfig: command not found sh: iwconfig: command not found sh: iwconfig: command not found sh: iwconfig: command not found sh: iwconfig: command not found sh: iwconfig: command not found sh: iwconfig: command not found sh: iwconfig: command not found sh: iwconfig: command not found sh: iwconfig: command not found ** (nautilus:13773): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «I»), avise a la lista de correo de gnome-vfs. sh: iwconfig: command not found sh: iwconfig: command not found --------------------------------------------------
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 ***