Bug 559792 – crash in Sudoku: finished the game

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 559792 - crash in Sudoku: finished the game


Summary:	crash in Sudoku: finished the game


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-07 19:25 UTC by delwinv
Modified:	2008-11-08 04:45 UTC

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

Description delwinv 2008-11-07 19:25:32 UTC

Version: 2.24.1

What were you doing when the application crashed?
finished the game


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 Tue Nov 4 19:33:06 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: crystalsvg

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 (81752 sec old) ---------------------
 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::212,TCPConnectionManager::access$900::46,TCPConnectionManager$5::runSupport::202,AEThread::run::71
java.net.SocketException: Protocol family unavailable
	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.addNewOutboundRequests(TCPConnectionManager.java:242)
	at com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager.mainLoop(TCPConnectionManager.java:212)
	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::Thu Nov 06 21:41:43 CET 2008::com.aelitis.azureus.core.networkmanager.impl.tcp.TCPConnectionManager::addNewOutboundRequests::242:
  ConnectDisconnectManager::address exception: full=/fe80:0:0:0:202:3fff:fed9:a94f:42758, hostname=fe80:0:0:0:202:3fff:fed9:a94f, port=42758, unresolved=false, full_sub=fe80:0:0:0:202:3fff:fed9:a94f/f
 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
...Too much output, ignoring rest...
--------------------------------------------------
Traceback (most recent call last):

+ Trace 209418

File "/var/lib/python-support/python2.5/gnome_sudoku/main.py", line 469 in you_win_callback
```
self.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-08 04:45:32 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 ***