Xpra: Ticket #20: client prints stuff forever after ^c
This may be related to #19,
Ignoring stray packet read after connection allegedly closed ([<object object at 0xb75114d0>, 'l4:drawi1ei2ei57ei1266ei886e5:rgb243365028:\x00\x00\x00\x00\x00\x00\x00'...])
We should not be getting so much stuff on a closed connection!
Wed, 07 Sep 2011 08:56:43 GMT - Antoine Martin: status changed
changed from new to accepted
This looks like the same problem as #19 and should also be fixed by r156.
Fri, 23 Sep 2011 14:38:12 GMT - Antoine Martin: status changed; resolution set
changed from accepted to closed
set to fixed
please re-open if this re-occurs, the read loop code also got some improvements in r166
Mon, 20 Feb 2012 19:59:24 GMT - Antoine Martin: version set
Sat, 23 Jan 2021 04:43:23 GMT - migration script:
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/20