GNOME Bugzilla – Bug 597963
crash in Window Selector: right click to configure...
Last modified: 2009-10-10 02:14:22 UTC
Version: 2.26.0 What were you doing when the application crashed? right click to configure window selector Distribution: Unknown Gnome Release: 2.26.0 2009-03-16 (GNOME) BugBuddy Version: 2.26.0 System: Linux 2.6.27.15-7-fl.smp.gcc4.1.x86.i686 #1 SMP Thu Feb 12 13:22:32 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10600000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 35151872 vsize: 35151872 resident: 13426688 share: 10547200 rss: 13426688 rss_rlim: 18446744073709551615 CPU usage: start_time: 1255170274 rtime: 35 utime: 9 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6e1e710 (LWP 2823)] 0xb7f1a424 in __kernel_vsyscall ()
+ Trace 218191
Thread 1 (Thread 0xb6e1e710 (LWP 2823))
---- Critical and fatal warnings logged during execution ---- ** Wnck **: wnck_screen_get_workspace_count: assertion `WNCK_IS_SCREEN (screen)' failed ----------- .xsession-errors (94 sec old) --------------------- Error: Can't find file "en_US.UTF-8" for symbols include Exiting Abandoning symbols file "(null)" ** (gnome-settings-daemon:2778): WARNING **: Could not activate the XKB configuration [35;01mwarning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.[0m [01mHP Linux Imaging and Printing System (ver. 3.9.2)[0m [01mSystem Tray Status Service ver. 2.0[0m Copyright (c) 2001-9 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 472773 ***