On windows, syncdaemon can't be stopped.

[Roberto Alsina]

If you start syncdaemon, and then try to stop it using "u1sdtool -q" or u1cp's tray context menu, it will not stop. Here's the output from syncdaemon:

2012-03-23 16:26:31,693 - twisted - ERROR - Failure: twisted.spread.pb.PBConnectionLost: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
Failure: twisted.spread.pb.PBConnectionLost: [Failure instance: Traceback (failure with no frames):
<class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
2012-03-23 16:26:31,694 - twisted - ERROR - ]
]
2012-03-23 16:26:31,696 - twisted - ERROR - *--- End of Failure #29 ---
*--- End of Failure #29 ---
2012-03-23 16:26:31,697 - ubuntuone.SyncDaemon.Pb - WARNING - Traceback is:
None
2012-03-23 16:26:31,698 - twisted - INFO - Stopping factory <twisted.spread.pb.PBClientFactory instance at 0x04239C60>
2012-03-23 16:26:31,704 - twisted - INFO - Main loop terminated.

This is a problem because syncdaemon is closing the IPC port but not closing its logs, so the next attempt to use it will activate a new instance, which will fail catastrophically with "I/O in closed file" errors because it can't log.

[Alejandro J. Cura (alecu)]

This is a problem with the network state detection code imported from Ubuntu SSO Client.
The NetworkManagerState class in windows creates a thread, and it never gets stopped.