Fix connecting to Wayland via WAYLAND_SOCKET #358
Merged
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.
This fixes a crash when
swww-daemon
is run using a Wayland connection socket provided through theWAYLAND_SOCKET
environment variable. (The easiest way of which I am aware to test this is to runwaypipe
--oneshot ssh localhost swww-daemon
). Before this changeswww-daemon
(commit 886ce3e) would produce the errorAfter this change, it should work (or possibly crash with EWouldBlock at a
super::wire::WireMsg::recv().unwrap())
, but that's a different issue I don't have time for today.)