GNOME Bugzilla – Bug 526257
crash in Chess: I can't run chess at all...
Last modified: 2008-04-05 02:08:57 UTC
Version: 2.20.1 What were you doing when the application crashed? I can't run chess at all, dunno why... Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- ** (gnome-app-install:17977): WARNING **: return value of custom widget handler was not a GtkWidget /usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1261: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed item.applications.set_default_sort_func(None) Window manager warning: Window 0x3402492 () sets an MWM hint indicating it isn't resizable, but sets min size 461 x 278 and max size 2147483647 x 2147483647; this doesn't make much sense. Window manager warning: Window 0x3402492 () sets an MWM hint indicating it isn't resizable, but sets min size 461 x 278 and max size 2147483647 x 2147483647; this doesn't make much sense. Another synaptic is running. Trying to bring it to the foreground Window manager warning: last_focus_time (466728949) is greater than comparison timestamp (466728947). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET /usr/lib/python2.5/site-packages/AppInstall/DialogComplete.py:201: GtkDeprecationWarning: gtk.TRUE is deprecated, use True instead gtk.main() Traceback (most recent call last):
+ Trace 194253
from glchess.glchess import start_game
-------------------------------------------------- Traceback (most recent call last):
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 412690 ***