Xpra: Ticket #2426: xpra start/shadow: fail-fast if screen exists already

https://lists.devloop.org.uk/pipermail/shifter-users/2019-September/002391.html

[i] One example is trying to start on a screen that already exists.

For [i], I would assume a fail-fast (instead of a timeout) client-side solution would quickly inform me that "try to attach instead". It could even automatically/interactively ask to do so?

The assumption here is that the server is remote (e.g. via ssh), so running the additional xpra list command is "a bit more complicated".



Thu, 26 Sep 2019 15:29:21 GMT - Antoine Martin: status changed

This may be easier with the paramiko backend? Using the proxy command return code to decide what to do?


Thu, 06 Feb 2020 06:36:02 GMT - Antoine Martin:

See also #2523.


Sun, 12 Apr 2020 16:07:54 GMT - Antoine Martin: status changed; resolution set

For details, see ticket:2523#comment:8


Sat, 23 Jan 2021 05:50:58 GMT - migration script:

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