After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 385937 - Sudoku crashed while playing a game
Sudoku crashed while playing a game
Status: RESOLVED FIXED
Product: gnome-games-superseded
Classification: Deprecated
Component: gnome-sudoku
2.17.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-14 17:57 UTC by Sebastien Bacher
Modified: 2006-12-28 22:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Sebastien Bacher 2006-12-14 17:57:15 UTC 
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gnome-games/+bug/75763

"See attached Files

Gnome-Sudoku crashed under what appeared to be normal conditions while filling in squares

http://librarian.launchpad.net/5395042/_usr_games_gnome-sudoku.1000.crash
Crash Log
...
Package: gnome-games 1:2.17.3-0ubuntu2
...
Traceback:
 Traceback (most recent call last):

+ Trace 94180

  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/gsudoku.py", line 1026 in entry_callback 
    self.remove(widget.x,widget.y)
  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/gsudoku.py", line 1107 in remove 
    del self.__error_pairs__[(x,y)]
  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/gsudoku.py", line 799 in __delitem__ 
    if k in self[i]: self[i].remove(k)  KeyError: (3, 5) ... http://librarian.launchpad.net/5395441/sudokucrash.png Screenshot of crash

The game did however carry on playing afterwards, although events (such as winning the game) did not appear to fire"
Comment 1 Andreas Røsdal 2006-12-26 10:08:46 UTC 
Thomas, do you know a way to fix this crash?
Comment 2 Thomas M. Hinkle 2006-12-28 22:35:08 UTC 
I recently committed a change to CVS that should prevent the traceback above. I'm still not entirely sure how the game got into a state such that it produced the traceback (i.e. I couldn't reproduce the problem), so I'm not 100% confident the underlying problem has been addressed, but the change I committed may well do the trick.