GNOME Bugzilla – Bug 544357
sudoku sometimes does not detect completed puzzle
Last modified: 2009-10-28 17:19:31 UTC
[ Forwarded from http://bugs.debian.org/489822 by Eric Cooper ] Sometimes sudoku does not realize I have completed a puzzle. It seems to occur when I use a tracker for a while, then revert to using no tracker. I fill in the final square, but it does not notice that the puzzle is complete. If I quit the program and then resume the saved game, as soon as I re-fill a square it detects that it's complete.
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 423478 ***
I don’t think it is the same bug. This one was reported with 2.22.2.1, which has the fix for bug#423478 included.
Josselin: I hadn't noticed that 423478 had been fixed. Thanks for pointing it out. Recent comments posted on bug 423478 suggest that it might not have fully fixed, so this could be a duplicate.
423478 has not been fixed. Workaround: if you delete any failed tracks by hand games complete OK. If you use the 'clear track' feature you (get/risk?) a game that does not realise it has been completed. The problem has been recognised as an error in the game record - can't remember the details. The corruption seems to come when a track is cleared by the button.
PS I do not understand why this is still unconfirmed - surely dupes confirm bugs?
http://bugs.debian.org/514781 may contain some valuable input to help fixing this bug. When sudoku is not detecting that the puzzle is completed, the user tried saving the game and restarting it later. He got this crash: Traceback (most recent call last):
+ Trace 213769
start_game()
main.start_game()
u = UI()
if self.select_game():
ret = fun(ui,*args,**kwargs)
choice = game_selector.NewOrSavedGameSelector().run_swallowed_dialog(self.swallower)
self.setup_dialog()
self.make_saved_game_model()
sudoku.sudoku_grid_from_string(g['game'].split('\n')[1].replace(' ','')).grid,
assert(len(s)<=GROUP_SIZE**2) AssertionError
Apparently, the saved session contains None instead of 0, somewhere in the array. This could explain this bug if this None appeared somewhere in the program state.
could be a dupe of bug 516491 as per comment#6
yes! *** This bug has been marked as a duplicate of bug 516491 ***