Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/run/user/<id>/wayland-0 does not exist - Wayland GUI applications do not work #448

Closed
Pleune opened this issue Apr 11, 2024 · 2 comments · Fixed by #450
Closed

/run/user/<id>/wayland-0 does not exist - Wayland GUI applications do not work #448

Pleune opened this issue Apr 11, 2024 · 2 comments · Fixed by #450
Labels
bug Something isn't working

Comments

@Pleune
Copy link

Pleune commented Apr 11, 2024

Bug description

With only the NixOS distribution, /mnt/wslg/runtime-dir contents are not linked to /run/user/<id>/. These links exist for Ubuntu/Debian/etc. WSL2 distributions. I can manually create these links, and wayland apps work perfectly. I cannot for the life of me figure out what component is supposed to create these links.

I think either something should be added to create these links, possibly as an override for the [email protected], or something is getting in the way of WSL2 creating these links.

In my other WSL2 distributions, the files are linked during the launching of the wsl command. when entering as root and starting a login shell or the regular user, the files are not linked. This makes me think that normally, the WSL2 subsystem goes in and creates these files, but I am not sure of this.

To Reproduce

Steps to reproduce the behavior:
Install NixOS WSL2 distrubution

WSL version

WSL version: 2.2.2.0
Kernel version: 5.15.150.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3296
@Pleune Pleune added the bug Something isn't working label Apr 11, 2024
@Pleune
Copy link
Author

Pleune commented Apr 11, 2024

One successful workaround from microsoft/WSL#8918 is to add the following configuation:

systemd.services."user-runtime-dir@" = {
  overrideStrategy = "asDropin";
  unitConfig.ConditionPathExists = "!/run/user/%i";
};

@nzbr
Copy link
Member

nzbr commented Apr 13, 2024

Interesting, this must have come with a recent update. I couldn't reproduce it on my install at first, but after updating I have the same problem. I'll make a PR to integrate the workaround

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants