Cancelled SOCKS5 file transfer not detected correctly

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start file transfer between 2 instances of Vacuum, via SOCKS5 Bytestreams, 
using PROXY.
2. Cancel file transfer at the TARGET side (which RECEIVES the file).

What is the expected output? What do you see instead?
It is expected that REQUESTER side will detect that connection is interrupted 
and will stop file transfer, changing its status to "File transfer cancelled by 
the other side". But the fact, that SOCKS5 connection is interrupted is not 
detected by REQUESTER, so the file transfer freezes, but REQUESTER still trying 
to send the file and display "File sending" status.

Original issue reported on code.google.com by yagimo...@gmail.com on 21 Dec 2010 at 4:10

[GoogleCodeExporter]

Original comment by potapov.s.a on 22 Dec 2010 at 5:23

• Changed state: Accepted
• Added labels: Type-Defect
• Removed labels: Type-Unknown

[GoogleCodeExporter]

It seems that it is Qt (4.6.3) bug, no signals emited and socket state is not 
changed when connection closed on receivers side.

Original comment by potapov.s.a on 26 Dec 2010 at 9:53

[GoogleCodeExporter]

fixed in r1702

Original comment by potapov.s.a on 21 Jan 2012 at 9:21

• Changed state: Fixed