GNOME Bugzilla – Bug 428831
crash in Panel: open console
Last modified: 2007-04-12 18:50:05 UTC
Version: 2.18.0 What were you doing when the application crashed? open console Distribution: Frugalware 0.7pre1 (Sayshell) Gnome Release: 2.18.0 2007-03-13 (Frugalware) BugBuddy Version: 2.18.1 System: Linux 2.6.20-fw5 #1 SMP PREEMPT Sat Mar 24 14:54:20 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mist Memory status: size: 33824768 vsize: 33824768 resident: 18354176 share: 12029952 rss: 18354176 rss_rlim: 4294967295 CPU usage: start_time: 1176336050 rtime: 141 utime: 128 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (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 -1226774848 (LWP 7741)] (no debugging symbols found) 0xb7f03410 in __kernel_vsyscall ()
+ Trace 127034
Thread 1 (Thread -1226774848 (LWP 7741))
----------- .xsession-errors (29 sec old) --------------------- (gnome-panel:7741): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8 Window manager warning: Property _NET_WM_NAME on window 0x1c00136 contained invalid UTF-8 Window manager warning: Property _NET_WM_ICON_NAME on window 0x1c00136 contained invalid UTF-8 (gnome-panel:7741): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8 (gnome-panel:7741): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8 (gnome-panel:7741): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8 (gimp:7879): Gimp-Widgets-WARNING **: GDK returned bogus values for the screen resolution, using 75 dpi instead. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 422662 ***