Xpra: Ticket #623: consistent and reliable client exit code and information

There can be many reasons why we close a connection. Unless this is simply a network failure which is an error and should be reported as such (and the client process should terminate with a non-zero exit code), we should generally be able to tell the user why the disconnection occurred. Most of the code is already there, it just needs to be constified so these values can be relied on.

Fri, 01 Aug 2014 09:20:34 GMT - Antoine Martin: owner changed

See r7075.

Please test, ie:

Some of the other disconnection messages can be a bit harder to trigger, see #614 for example.

Will that do?

Fri, 01 Aug 2014 16:32:07 GMT - Antoine Martin:

As of r7088, the server-side messages are nicer and the client tries to tell the server when it is exiting and why, ie:

client Protocol(SocketConnection(/home/antoine/.xpra/desktop-10)) has requested disconnection: exit on signal SIGINT

client Protocol(SocketConnection(/home/antoine/.xpra/desktop-10)) has requested disconnection: client exit

Sun, 17 Aug 2014 14:22:33 GMT - Antoine Martin: priority changed

Should be closed for v0.14.x, raising to critical.

Tue, 19 Aug 2014 03:34:17 GMT - Antoine Martin: milestone changed

Should be closed against milestone 0.14

Mon, 27 Oct 2014 17:52:27 GMT - Antoine Martin:


Tue, 25 Nov 2014 19:34:26 GMT - Scott Bennett: status changed; resolution set

Verified and tested in 0.14.12, thank you

Sat, 23 Jan 2021 05:01:11 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/623