[regression] code to open local display in waitforx is broken by recent libxcb #3336
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to @derekschrock for raising this as a comment to #3297
Commit 80fab03 introduced a way to prevent waitforx going to the network when trying to open a display, and hence potentially blocking.
This method turned out to be invalidated by libxcb version 1.16 and 1.17
This change adds an explicit check that the Unix socket for the display in
/tmp/.X11-unix/Xn
is open before trying to connect to display ':n'. This has the same effect.In the original change I was keen to avoid a dependency on the string
"/tmp/.X11-unix/X%d"
for converting a display number to a unix socket. This was unjustified, as many other utilities assume this string, including ssh:-