GNOME Bugzilla – Bug 509203
crash in Computer: positionnement sur le ré...
Last modified: 2008-01-13 23:21:59 UTC
Version: 2.18.3 What were you doing when the application crashed? positionnement sur le répertoire :/../téléchargement qui s'affichait /../t?l?chargement Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 86269952 vsize: 86269952 resident: 26603520 share: 16318464 rss: 26603520 rss_rlim: 4294967295 CPU usage: start_time: 1200255177 rtime: 2622 utime: 2434 stime: 188 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 0xb6dd66b0 (LWP 2799)] (no debugging symbols found) 0xb762b321 in waitpid () from /lib/libpthread.so.0
+ Trace 185191
Thread 1 (Thread 0xb6dd66b0 (LWP 2799))
----------- .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:2799): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 52: Invalid UTF-8 encoded text - not valid 'Choisissez une application pour ouvrir <i> (nautilus:2799): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 52: 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 ***