GNOME Bugzilla – Bug 518225
crash in Sudoku: opening the sudoku game ...
Last modified: 2008-02-23 18:57:22 UTC
Version: 2.20.1 What were you doing when the application crashed? opening the sudoku game while updateing the system 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 23:05:12 GMT 2007 i686 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 (7 sec old) --------------------- /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) Another synaptic is running. Trying to bring it to the foreground Window manager warning: Window 0x3403533 () 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 0x3403533 () 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 ** (synaptic:5622): WARNING **: no statusfd changes/content updates in terminal for 120 seconds ** (synaptic:5622): WARNING **: TerminalTimeout in step: Configuring capplets-data SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSTraceback (most recent call last):
+ Trace 190183
from gnome_sudoku.gnome_sudoku 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 418427 ***