GNOME Bugzilla – Bug 552396
crash in File Browser:
Last modified: 2008-09-16 10:34:40 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola Memory status: size: 67293184 vsize: 67293184 resident: 31694848 share: 16097280 rss: 31694848 rss_rlim: 4294967295 CPU usage: start_time: 1221502334 rtime: 267 utime: 253 stime: 14 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 0xb6af5720 (LWP 6531)] (no debugging symbols found) 0xb7f21424 in __kernel_vsyscall ()
+ Trace 206805
Thread 1 (Thread 0xb6af5720 (LWP 6531))
----------- .xsession-errors --------------------- QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image QImage::smoothScale: Image is a null image ** (nautilus:6341): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «opt-snc»), avise a la lista de correo de gnome-vfs. Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:6531): WARNING **: No se encontró descripción para el tipo MIME «x-directory/smb-share» (el archivo es «opt-snc»), 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 ***