GNOME Bugzilla – Bug 625773
crash in Window List: I had right-clicked on t...
Last modified: 2010-08-02 22:26:03 UTC
Version: 2.30.0 What were you doing when the application crashed? I had right-clicked on the virtual workspace icon (the plan was to change from 2 virtual screens to 4). Distribution: Unknown Gnome Release: 2.30.0 2010-05-11 (Foresight Linux) BugBuddy Version: 2.30.0 System: Linux 2.6.33.6-3-fl.smp.gcc4.1.x86.i686 #1 SMP Wed Jul 7 23:13:07 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10800000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glider Icon Theme: default.kde GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 79298560 vsize: 79298560 resident: 13869056 share: 11079680 rss: 13869056 rss_rlim: 18446744073709551615 CPU usage: start_time: 1280621149 rtime: 381 utime: 328 stime: 53 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 0xb66097e0 (LWP 1329)] 0xb779c424 in __kernel_vsyscall ()
+ Trace 223067
Thread 1 (Thread 0xb66097e0 (LWP 1329))
---- Critical and fatal warnings logged during execution ---- ** Wnck **: wnck_screen_get_workspace_count: assertion `WNCK_IS_SCREEN (screen)' failed ----------- .xsession-errors (63 sec old) --------------------- (exe:2894): Gdk-WARNING **: XID collision, trouble ahead (exe:2894): Gdk-WARNING **: XID collision, trouble ahead (exe:2894): Gdk-WARNING **: XID collision, trouble ahead (exe:2894): Gdk-WARNING **: XID collision, trouble ahead (exe:2894): Gdk-WARNING **: XID collision, trouble ahead (exe:2894): Gdk-WARNING **: XID collision, trouble ahead (exe:2894): Gdk-WARNING **: XID collision, trouble ahead (exe:2894): Gdk-WARNING **: XID collision, trouble ahead --------------------------------------------------
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 bug 472773 ***