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 703335 - gnome-sudoku crashes when attempt to start new game after another
gnome-sudoku crashes when attempt to start new game after another
Status: RESOLVED FIXED
Product: gnome-sudoku
Classification: Applications
Component: general
3.12.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-sudoku-maint
gnome-sudoku-maint
Depends on:
Blocks:
 
 
Reported: 2013-06-30 06:17 UTC by andré
Modified: 2014-06-29 20:23 UTC
See Also:
GNOME target: ---
GNOME version: 3.3/3.4

Attachments
Fix exception when starting new game (2.32 KB, patch)
2014-06-29 20:23 UTC, Michael Catanzaro 		committed Details | Review

Description andré 2013-06-30 06:17:45 UTC 
Note that the version of gnome-sudoku is actually 3.4.1.
(That version wasn't available as an option.)

It is running on python 2.7.3.

After finishing a sudoku game, and choosing to run another via either the icon or the menu, it often but not always crashes.

In the console, it displays :
----
(gnome-sudoku:19059): Gtk-CRITICAL **: gtk_container_add: assertion `GTK_IS_CONTAINER (container)' failed  avertissement
123
Traceback (most recent call last):  erreur-critique

+ Trace 232170

  • File "/usr/lib/python2.7/site-packages/gnome_sudoku/main.py", line 842 in selection_changed_cb 
    self.main_ui.gsd.cover_track()
  • File "/usr/lib/python2.7/site-packages/gnome_sudoku/gsudoku.py", line 710 in cover_track 
    self.grid.remove(*coord)
AttributeError: 'NoneType' object has no attribute 'remove' 

sh: bug-buddy : commande introuvable
----

bug-buddy is not installed.

I have noticed that it doesn't seem to crash if the "apply" button at the bottom toward the right is dimmed.  Otherwise it seems to crash every time.

If the button is not dimmed, that usually (but not necessarily) means that the follow option was used, to display guesses in a different colour.

In any case, an effective workaround to avoid a crash seems to be pressing the "apply" button it until it dims, whenever it is not already dimmed.
Each time that button is pressed, and the current colour isn't black, all boxes of the current colour will be changed to black, and the current colour removed.
Comment 1 Michael Catanzaro 2014-06-29 20:23:37 UTC 
I'm mostly papering over this, but that's fine since this code has all been removed from the next version.

Thanks for taking the time to report this bug.

The following fix has been pushed:
62dd0cc Fix exception when starting new game
Comment 2 Michael Catanzaro 2014-06-29 20:23:40 UTC 
Created attachment 279560 [details] [review]
Fix exception when starting new game