can't start wslg

[yuzhegan]

IMPORTANT
Please read README and Docs before creating the issue.

Please fill out the below information:
Describe the issue
A clear and concise description of what the bug is.
can't start wslg
To Reproduce
Steps to reproduce the behavior:
i had add set -Ux DISPLAY (cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0 to config.fish
Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.


Enviroment:

• Windows build number: [e.g. 10.0.17134.228] (Type ver at a Command Prompt)
• Security Software: [e.g. ESET Internet Security]
• WSL version 1/2: [e.g. WSL1]
• ArchWSL version [e.g. 19.3.7.0]
• ArchWSL Installer type zip/appx/other clean/update [e.g. appx update]
• Launcher version [e.g. 19030700] (Type Arch.exe version at a Command Prompt)

Additional context
Add any other context about the problem here.

[wallacewinfrey]

The fix mentioned here resolves for both Windows-native X11 servers and wslg

[dinesh-58]

maybe try export DISPLAY=:0 and using the workaround suggested in #342. That worked for me

[Qiyue0726]

Maybe WSLG needs to install the Wayland package

[drannex42]

This is what fixes it for me: microsoft/WSL#6999

@/Nahor In the interest of saving others from this unfortunate bad default behaviour who find this GH issue, an easy manual fix is to create /etc/tmpfiles.d/wslg.conf as root with the following contents:

#  This file is part of the debianisation of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2 of the License, or
#  (at your option) any later version.

# See tmpfiles.d(5) for details

# Type Path           Mode UID  GID  Age Argument
L+     /tmp/.X11-unix -    -    -    -   /mnt/wslg/.X11-unix

and then wsl --shutdown and start it again to see the effect.

This results in the symlink being created, and it happens after tmpfs is mounted by systemd.