GNOME Bugzilla – Bug 508107
crash in Computer: regarder l'espace disk ...
Last modified: 2008-01-09 08:46:00 UTC
Version: 2.18.3 What were you doing when the application crashed? regarder l'espace disk retant Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 466399232 vsize: 466399232 resident: 32530432 share: 16928768 rss: 32530432 rss_rlim: 18446744073709551615 CPU usage: start_time: 1199825066 rtime: 289 utime: 263 stime: 26 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2afb7a3d3540 (LWP 4421)] (no debugging symbols found) 0x00002afb7395834f in waitpid () from /lib/libpthread.so.0
+ Trace 184556
Thread 1 (Thread 0x2afb7a3d3540 (LWP 4421))
----------- .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:4421): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 58: Invalid UTF-8 encoded text - not valid 'Choisissez une application pour ouvrir <i> (nautilus:4421): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 58: Invalid UTF-8 encoded text - not valid 'Choisissez une application pour ouvrir <i> --------------------------------------------------
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 ***