Bug 594316 – crash in Sudoku: dont know

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 594316 - crash in Sudoku: dont know


Summary:	crash in Sudoku: dont know


Status:	RESOLVED DUPLICATE of bug 516491

Product:	gnome-games-superseded
Classification:	Deprecated
Component:	gnome-sudoku
Version:	1.4.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	GNOME Games maintainers
QA Contact:	GNOME Games maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-09-06 15:26 UTC by catherine
Modified:	2009-09-06 17:20 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description catherine 2009-09-06 15:26:36 UTC

Version: 2.24.1.1

What were you doing when the application crashed?
dont know


Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.24.1 2008-10-24 (Ubuntu)
BugBuddy Version: 2.24.1

System: Linux 2.6.27-14-generic #1 SMP Tue Aug 18 16:25:45 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
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 ---------------------
    if self.select_game():

+ Trace 217364

File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 60 in _
```
ret = fun(ui,*args,**kwargs)
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 209 in select_game
```
choice = game_selector.NewOrSavedGameSelector().run_swallowed_dialog(self.swallower)
```
File "/var/lib/python-support/python2.5/gnome_sudoku/game_selector.py", line 191 in run_swallowed_dialog
```
self.setup_dialog()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/game_selector.py", line 76 in setup_dialog
```
self.make_saved_game_model()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/game_selector.py", line 151 in make_saved_game_model
```
sudoku.sudoku_grid_from_string(g['game'].split('\n')[1].replace(' ','')).grid,
```

File "/var/lib/python-support/python2.5/gnome_sudoku/sudoku.py", line 232 in sudoku_grid_from_string

assert(len(s)<=GROUP_SIZE**2) AssertionError -------------------------------------------------- Traceback (most recent call last):

File "/usr/games/gnome-sudoku", line 50 in <module>
```
start_game()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/gnome_sudoku.py", line 21 in start_game
```
main.start_game()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 1051 in start_game
```
u = UI()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 195 in __init__
```
if self.select_game():
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 60 in _
```
ret = fun(ui,*args,**kwargs)
```
File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 209 in select_game
```
choice = game_selector.NewOrSavedGameSelector().run_swallowed_dialog(self.swallower)
```
File "/var/lib/python-support/python2.5/gnome_sudoku/game_selector.py", line 191 in run_swallowed_dialog
```
self.setup_dialog()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/game_selector.py", line 76 in setup_dialog
```
self.make_saved_game_model()
```
File "/var/lib/python-support/python2.5/gnome_sudoku/game_selector.py", line 151 in make_saved_game_model
```
sudoku.sudoku_grid_from_string(g['game'].split('\n')[1].replace(' ','')).grid,
```
File "/var/lib/python-support/python2.5/gnome_sudoku/sudoku.py", line 232 in sudoku_grid_from_string
```
assert(len(s)<=GROUP_SIZE**2) AssertionError
```

Comment 1 Fabio Durán Verdugo 2009-09-06 17:20:38 UTC

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 bug 516491 ***