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 559398 - crash in Sudoku: Having reloaded a puzzle...
crash in Sudoku: Having reloaded a puzzle...
Status: RESOLVED DUPLICATE of bug 557308
Product: gnome-games-superseded
Classification: Deprecated
Component: gnome-sudoku
2.24.x
Other All
: High critical
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-05 11:11 UTC by ubuntu
Modified: 2008-11-05 12:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description ubuntu 2008-11-05 11:11:38 UTC 
Version: 2.24.1

What were you doing when the application crashed?
Having reloaded a puzzle which had been saved under 8.04, before an upgrade to 8.10, I then clicked on "New" on the toolbar. The game immediately crashed. This behaviour is repeatable. It still occurs if the reloaded game is modified before "New". How do I remove this saved puzzle?


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

System: Linux 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 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 ---------------------
Traceback (most recent call last):

+ Trace 209269

  • File "/var/lib/python-support/python2.5/gnome_sudoku/timer.py", line 139 in window_state_event_cb 
    self.toggle_timing(False)
  • File "/var/lib/python-support/python2.5/gnome_sudoku/timer.py", line 154 in toggle_timing 
    self.tot_time_complete += end_time - self.__absolute_start_time__
TypeError: unsupported operand type(s) for +=: 'NoneType' and 'float' 
Traceback (most recent call last):

+ Trace 209269

  • File "/var/lib/python-support/python2.5/gnome_sudoku/timer.py", line 139 in window_state_event_cb 
    self.toggle_timing(False)
  • File "/var/lib/python-support/python2.5/gnome_sudoku/timer.py", line 154 in toggle_timing 
    self.tot_time_complete += end_time - self.__absolute_start_time__
TypeError: unsupported operand type(s) for +=: 'NoneType' and 'float' 
--------------------------------------------------
Traceback (most recent call last):

+ Trace 209269

  • File "/var/lib/python-support/python2.5/gnome_sudoku/timer.py", line 139 in window_state_event_cb 
    self.toggle_timing(False)
  • File "/var/lib/python-support/python2.5/gnome_sudoku/timer.py", line 154 in toggle_timing 
    self.tot_time_complete += end_time - self.__absolute_start_time__
TypeError: unsupported operand type(s) for +=: 'NoneType' and 'float' 






Comment 1


Jesse Zhang





          2008-11-05 12:17:13 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 557308 ***