GNOME Bugzilla – Bug 522045
crash in Computer: Crash each time I ask fo...
Last modified: 2008-03-13 00:35:42 UTC
Version: 2.18.3 What were you doing when the application crashed? Crash each time I ask for a folder properties on my USB-key. This USB-key contains only two empty folders, named "album" and "dcim". No strange characters are thus present, AFAI can see, in these folders names. Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (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: Default Icon Theme: gnome Memory status: size: 77033472 vsize: 77033472 resident: 22097920 share: 13766656 rss: 22097920 rss_rlim: 4294967295 CPU usage: start_time: 1205337087 rtime: 352 utime: 326 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 0xb6d646b0 (LWP 11457)] (no debugging symbols found) 0xb75b9321 in waitpid () from /lib/libpthread.so.0
+ Trace 192230
Thread 1 (Thread 0xb6d646b0 (LWP 11457))
----------- .xsession-errors (3708389 sec old) --------------------- (gnome-panel:11232): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8 (gnome-panel:11232): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8 (gnome-panel:11232): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8 Avertissement du gestionnaire de fenêtres : La propriété _NET_WM_NAME de la fenêtre 0x2058804 contient un code UTF-8 non valide Avertissement du gestionnaire de fenêtres : La propriété _NET_WM_ICON_NAME de la fenêtre 0x2058804 contient un code UTF-8 non valide (gnome-panel:11232): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8 ...Too much output, ignoring rest... --------------------------------------------------
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 ***