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 396823 - Sudoku crashes (certainly after "clear All")
Sudoku crashes (certainly after "clear All")
Status: RESOLVED FIXED
Product: gnome-games-superseded
Classification: Deprecated
Component: gnome-sudoku
2.17.x
Other Linux
: Urgent normal
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-15 10:50 UTC by Daniel Holbach
Modified: 2007-01-16 01:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Daniel Holbach 2007-01-15 10:50:23 UTC 
Forwarded from: https://launchpad.net/ubuntu/+source/gnome-games/+bug/79366

 Traceback (most recent call last):

+ Trace 102346

  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/gnome_sudoku.py", line 578 in clear_cb
  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/gtk_goodies/Undo.py", line 43 in perform
  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/gnome_sudoku.py", line 574 in <lambda>
  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/gsudoku.py", line 961 in reset_grid
  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/gsudoku.py", line 1131 in remove
  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/gsudoku.py", line 1098 in add_value
  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/sudoku.py", line 535 in add
  • File "/usr/lib/python2.4/site-packages/gnome_sudoku/sudoku.py", line 123 in add 
    ConflictError: (1, (0, 3), 5)






Comment 1


Andreas Røsdal





          2007-01-15 21:46:11 UTC
        



This should be fairly easy to fix, based on the good traceback from Python.
But I'd like to reproduce the crash, do you know how to reproduce it?






Comment 2


Thomas M. Hinkle





          2007-01-16 01:13:02 UTC
        



I wasn't able to perfectly reproduce this, but I did fix up the code in the traceback so that any error like this would be caught and properly handled. I also found some other bugginess when using clear and undo on a grid with conflicts in it (the situation that seemed to trigger this bug). I've just committed a fix that  makes clearing and undoing-the-clear work properly on a grid with conflicts.