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 521828 - crash in Sudoku: Well, I had accidentally...
crash in Sudoku: Well, I had accidentally...
Status: RESOLVED DUPLICATE of bug 430893
Product: gnome-games-superseded
Classification: Deprecated
Component: gnome-sudoku
2.20.x
Other All
: High critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-11 18:04 UTC by unstained
Modified: 2008-04-07 17:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description unstained 2008-03-11 18:04:33 UTC 
Version: 2.20.1

What were you doing when the application crashed?
Well, I had accidentally "Cleared Other" from the tracker side bar.  When used Undo, it replaced all the numbers in the tracker color rather than black.  I kept playing for a while, then wanted them to be black again, so I did "Clear Tracker" switched to "No Tracker" then tried undo and it died.


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.1 2007-10-19 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Tue Feb 12 02:46:46 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
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 ---------------------
    self[index].inverse()

+ Trace 192103

  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gtk_goodies/Undo.py", line 54 in inverse 
    u.perform()
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gtk_goodies/Undo.py", line 43 in perform 
    self.action(*self.action_args)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 946 in <lambda> 
    lambda *args: [self.main_ui.gsd.add_value(*entry) for entry in self.main_ui.cleared.pop()],
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1119 in add_value 
    self.grid.add(x,y,val,True)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 549 in add 
    SudokuGrid.add(self,x,y,val,*args,**kwargs)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 124 in add 
    raise ConflictError(TYPE_ROW,(x,y),val)
ConflictError: (0, (7, 7), None) 
--------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/gnome_sudoku/gtk_goodies/Undo.py", line 281, in undo
    self[index].inverse()

+ Trace 192103

  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gtk_goodies/Undo.py", line 54 in inverse 
    u.perform()
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gtk_goodies/Undo.py", line 43 in perform 
    self.action(*self.action_args)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py", line 946 in <lambda> 
    lambda *args: [self.main_ui.gsd.add_value(*entry) for entry in self.main_ui.cleared.pop()],
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1119 in add_value 
    self.grid.add(x,y,val,True)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 549 in add 
    SudokuGrid.add(self,x,y,val,*args,**kwargs)
  • File "/usr/lib/python2.5/site-packages/gnome_sudoku/sudoku.py", line 124 in add 
    raise ConflictError(TYPE_ROW,(x,y),val)
ConflictError: (0, (7, 7), None) 






Comment 1


Gianluca Borello





          2008-04-07 17:17:12 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 430893 ***