Resuming from sleep doesn't recover nicely

[GoogleCodeExporter]

Steps to reproduce:

1. Have a saved, valid profile with it set to auto connect.
2. Connect to server
3. Let PC go to sleep (mine is 30 minutes) with transmission-remote-dotnet 
minimized to system tray
4. Upon return, transmission-remote-dotnet immediately complains with the 
attached error.

It appears the client is immediately and aggressively trying to reconnect after 
it returns from waking up.  The Windows 7 IP Stack isn't online at this point 
so it instantly fails the connects.

It's expected for the IP stack to take roughly 3 seconds to properly start 
after resuming from standby (it takes ~ 3 seconds on every PC I own).

I propose it's probably expected behavior for the client to wait until the IP 
stack is correctly online and for the client to cleanly reconnect in the system 
tray.  

Clicking OK on the error, and then hitting "reconnect" successfully connects 
because obviously the IP stack has initialized by then.

Is there a way to properly determine "the PC is resuming from standby, IP stack 
isn't ready ... waiting 3 seconds then trying"?

What version of the products are you using?
OS: Windows 7 Professional, 64bit
Transmission: 3.24 (build 0)
Remote: 2.13 (rev 11501)

Original issue reported on code.google.com by plat...@gmail.com on 7 Jan 2011 at 10:23

Attachments:

• transmission-remote-dotnet-sleepbug.png

[GoogleCodeExporter]

question: after resuming, you cant ping localhost until IP stack isn't ready, 
right?

Original comment by elso.and...@gmail.com on 7 Jan 2011 at 3:14

• Changed state: Accepted

[GoogleCodeExporter]

I don't know if you can ping localhost or not within that window.  

By the time run starts up and you get to typing "ping localhost" it's probably 
already online.  

After clicking the Mouse, about 800ms later you hear a the error noise from 
transmission-remote-dotnet with the error.

Original comment by plat...@gmail.com on 7 Jan 2011 at 3:18

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Found a vmware to test this. Added by r715.
Please send a feedback, whether it goes with you.

Original comment by elso.and...@gmail.com on 7 Jan 2011 at 7:48

[GoogleCodeExporter]

I saw this a lot until I built from source in April, prior to that I was using 
the installer from last year sometime.  Since then I have not seen the error at 
all.  

However, it does not auto-connect either, it needs manual re-connection.  I 
guess it would be nice to auto-re-connect if TRD was connected when the machine 
went into sleep.  

Either way, not having the error message is a good improvement.

Original comment by aikido...@gmail.com on 6 Aug 2011 at 10:04