GNOME Bugzilla – Bug 537286
crash in File Browser: navegando en internet
Last modified: 2008-06-09 09:30:08 UTC
Version: 2.20.0 What were you doing when the application crashed? navegando en internet 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: Wasp Icon Theme: TuxnTosh Memory status: size: 133922816 vsize: 133922816 resident: 27410432 share: 17469440 rss: 27410432 rss_rlim: 4294967295 CPU usage: start_time: 1212931617 rtime: 242 utime: 229 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 0xb6be0720 (LWP 3299)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199881
Thread 1 (Thread 0xb6be0720 (LWP 3299))
----------- .xsession-errors --------------------- return codecs.utf_8_decode(input, errors, True) UnicodeDecodeError: 'utf8' codec can't decode bytes in position 534-536: invalid data ** Message: failed to load session from /home/luisana/.nautilus/saved-session-UUK35T (nautilus:3167): Eel-WARNING **: No extension, not implemented yet ** (x-session-manager:3079): WARNING **: Host name lookup failure on localhost. seahorse nautilus module initialized Initializing gnome-mount extension (nautilus:3260): Eel-WARNING **: No extension, not implemented yet seahorse nautilus module initialized Initializing gnome-mount extension (nautilus:3299): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 ***