GNOME Bugzilla – Bug 510349
crash in File Browser: collegato Muvo V200, tas...
Last modified: 2008-01-18 15:36:57 UTC
Version: 2.18.3 What were you doing when the application crashed? collegato Muvo V200, tasto destro sull'icona, "proprietà" ==> crash ! 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: Clearlooks Icon Theme: gnome Memory status: size: 76480512 vsize: 76480512 resident: 26640384 share: 15794176 rss: 26640384 rss_rlim: 4294967295 CPU usage: start_time: 1200646994 rtime: 637 utime: 594 stime: 43 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 0xb6da26b0 (LWP 3212)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185795
Thread 1 (Thread 0xb6da26b0 (LWP 3212))
----------- .xsession-errors (1155 sec old) --------------------- Avviso del window manager: La proprietà _NET_WM_NAME della finestra 0x2800022 contiene UTF-8 non valido Avviso del window manager: La proprietà _NET_WM_ICON_NAME della finestra 0x2800022 contiene UTF-8 non valido (gnome-panel:3208): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8 (gnome-panel:3208): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8 (gnome-panel:3208): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8 Avviso del window manager: La proprietà _NET_WM_NAME della finestra 0x2800022 contiene UTF-8 non valido Avviso del window manager: La proprietà _NET_WM_ICON_NAME della finestra 0x2800022 contiene UTF-8 non valido ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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 ***