Bug 559030 – crash in Sudoku:

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 559030 - crash in Sudoku:


Summary:	crash in Sudoku:


Status:	RESOLVED DUPLICATE of bug 557308

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-11-03 02:05 UTC by mlmaher
Modified:	2008-11-03 05:10 UTC

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

Description mlmaher 2008-11-03 02:05:58 UTC

Version: 2.24.1

What were you doing when the application 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 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 (158124 sec old) ---------------------
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.access$900(TCPConnectionManager.java:46)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager$5.runSupport(TCPConnectionManager.java:202)
	at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:71)
DEBUG::Sat Nov 01 01:10:07 CDT 2008::com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager::runSelect::537:
  ConnectDisconnectManager::address exception: full=/228.94.173.68:24018, hostname=228.94.173.68, port=24018, unresolved=false, full_sub=228.94.173.68/228.94.173.68, host_address=228.94.173.68
 channel=java.nio.channels.SocketChannel[closed], socket=Socket[unconnected], local_address=0.0.0.0/0.0.0.0, local_port=-1, remote_address=<null>, remote_port=0
    TCPConnectionManager::mainLoop::213,TCPConnectionManager::access$900::46,TCPConnectionManager$5::runSupport::202,AEThread::run::71
java.net.SocketException: Network is unreachable
	at sun.nio.ch.Net.connect(Native Method)
	at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:525)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.addNewRequest(TCPConnectionManager.java:311)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.runSelect(TCPConnectionManager.java:537)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.mainLoop(TCPConnectionManager.java:213)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.access$900(TCPConnectionManager.java:46)
...Too much output, ignoring rest...
--------------------------------------------------
Traceback (most recent call last):

+ Trace 209134

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 Jesse Zhang 2008-11-03 05:10:25 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 ***