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 507810 - crash in Sudoku: trying to play a new gam...
crash in Sudoku: trying to play a new gam...
Status: RESOLVED DUPLICATE of bug 493886
Product: gnome-games-superseded
Classification: Deprecated
Component: gnome-sudoku
2.21.x
Other All
: High critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-07 11:28 UTC by rase_jean_charles
Modified: 2008-01-10 22:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description rase_jean_charles 2008-01-07 11:28:26 UTC
Version: 2.21.2

What were you doing when the application crashed?
trying to play a new game


Distribution: Mandriva Linux release 2008.0 (Official) for x86_64
Gnome Release: 2.20.0 2007-09-19 (Mandriva)
BugBuddy Version: 2.20.0

System: Linux 2.6.22.12-desktop-1mdv #1 SMP Tue Nov 20 13:15:05 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Blue
Icon Theme: gnome

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 ---------------------
    ret = fun(ui,*args,**kwargs)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 212 in select_game
    self.gsd.change_grid(choice[1],9)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1016 in change_grid
    self.setup_grid(grid,group_size)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1048 in setup_grid
    self.grid = sudoku.InteractiveSudoku(grid,group_size=group_size)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 614 in __init__
    SudokuSolver.__init__(self,grid,verbose,group_size)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 255 in __init__
    SudokuGrid.__init__(self,grid,verbose=verbose,group_size=group_size)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 92 in __init__
    grid.append([int(i) for i in g[start:start+side]])
ValueError: invalid literal for int() with base 10: ''
--------------------------------------------------
Traceback (most recent call last):
  File "/usr/bin/gnome-sudoku", line 36, in <module>
    start_game()
  File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 1008, in start_game
    u = UI()
  File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 192, in __init__
    if self.select_game():
  File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 64, in _
    ret = fun(ui,*args,**kwargs)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 212 in select_game
    self.gsd.change_grid(choice[1],9)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1016 in change_grid
    self.setup_grid(grid,group_size)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1048 in setup_grid
    self.grid = sudoku.InteractiveSudoku(grid,group_size=group_size)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 614 in __init__
    SudokuSolver.__init__(self,grid,verbose,group_size)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 255 in __init__
    SudokuGrid.__init__(self,grid,verbose=verbose,group_size=group_size)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 92 in __init__
    grid.append([int(i) for i in g[start:start+side]])
ValueError: invalid literal for int() with base 10: ''

Comment 1 Thomas Andersen 2008-01-10 22:19:49 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 493886 ***