GNOME Bugzilla – Bug 509425
crash in File Browser: Le di al boton derecho p...
Last modified: 2008-01-14 23:51:16 UTC
Version: 2.18.3 What were you doing when the application crashed? Le di al boton derecho propiedades Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 75571200 vsize: 75571200 resident: 25665536 share: 15794176 rss: 25665536 rss_rlim: 4294967295 CPU usage: start_time: 1200330806 rtime: 522 utime: 478 stime: 44 cutime:886 cstime: 69 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 0xb6dfe6b0 (LWP 3946)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185313
Thread 1 (Thread 0xb6dfe6b0 (LWP 3946))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (nautilus:3946): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 50: Invalid UTF-8 encoded text - not valid 'Seleccione una aplicación para abrir <i>1 (nautilus:3946): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 50: Invalid UTF-8 encoded text - not valid 'Seleccione una aplicación para abrir <i>1 --------------------------------------------------
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 355018 ***