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 558664 - crash in Sudoku: I was moving around the ...
crash in Sudoku: I was moving around the ...
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-10-31 13:53 UTC by jtv
Modified: 2008-11-01 12:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description jtv 2008-10-31 13:53:19 UTC 
Version: 2.24.1

What were you doing when the application crashed?
I was moving around the playing field using the cursor keys (the "up" key).  If I remember correctly I was just expecting key repeat to kick in when the game crashed.


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 Fri Oct 24 06:40:41 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
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 (90093 sec old) ---------------------
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
08-10-30 19:49:17 (WARNING): GtkSpinButton: setting an adjustment with non-zero page size is deprecated
...Too much output, ignoring rest...
--------------------------------------------------
Traceback (most recent call last):

+ Trace 208965

  • File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 853 in autosave 
    self.sudoku_tracker.save_game(self)
  • File "/var/lib/python-support/python2.5/gnome_sudoku/saver.py", line 130 in save_game 
    jar = jar_game(ui)
  • File "/var/lib/python-support/python2.5/gnome_sudoku/saver.py", line 34 in jar_game 
    ui.timer.finish_timing()
  • File "/var/lib/python-support/python2.5/gnome_sudoku/timer.py", line 166 in finish_timing 
    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


Susana





          2008-11-01 12:15:28 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 ***