Xpra: Ticket #1535: displayfd switch for xpra

We can now start servers via the proxy (#1105) and this may well become the default. Since we may not know the actual X11 display in advance (we rely on Xorg -displayfd, #172), we check for new sockets and probe them. A better way would be to provide a "--displayfd" switch and write the display to this file descriptor.

Tue, 20 Jun 2017 16:16:55 GMT - Antoine Martin: priority, status, milestone changed

priority changed from major to critical
status changed from new to assigned
milestone changed from 3.0 to 2.2

Would really help speedup the start-via-proxy feature (#1105 aka logind multiseat), so raising.

Fri, 04 Aug 2017 13:24:05 GMT - Antoine Martin: attachment set

attachment set to displayfd-v6.patch

work in progress - doesn't like daemon=yes

Fri, 04 Aug 2017 14:47:21 GMT - Antoine Martin: status changed; resolution set

status changed from assigned to closed
resolution set to fixed

Done in r16612.

Not as useful as I thought it was going to be: we still have to go through the identify_new_socket code because the display may not be available when we get the display value back (sockets take time, may not be accessible, etc).

But at least things should be more reliable than before. This feature may also be used for other purposes.

Sat, 05 Aug 2017 18:11:36 GMT - Antoine Martin:

Minor related fixes:

r16636: honour displayfd with "request-start" mode (start via system wide proxy)
r16631: ignore displayfd=0 (the default), don't try to write there!

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

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