/tmp/.X11-unit/X0 auto removed a few minutes after the wsl2 starts

[Shengyis]

Windows Version

Microsoft Windows [Version 10.0.22631.4037]

WSL Version

WSL version: 2.2.4.0, WSLg version: 1.0.61

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Archlinux

Other Software

No response

Repro Steps

wsl --shutdown
wsl -d Arch

just reboot wsl and enter the distro

Expected Behavior

there should be a soft link : /tmp/.X11-unit/X0 to /mnt/wslg/.X11-unit/X0

Actual Behavior

when enter the distro:

ls -l /tmp/.X11-unix

shows that X0 exists, it is the same file as /mnt/wslg/.X11-unit/X0, after few minutes,

ls -l /tmp/.X11-unix

again X0 disappear, then I can not ran any gui related command. I need manually create a soft link to /mnt/wslg/.X11-unit/X0 every time.

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• The contents of /tmp are cleared few seconds after start up (#11739), similarity score: 0.74
• Upgrade from 0.70.4 to 1.0 kills /tmp/.X11/X0 iff systemd is enabled (#9158), similarity score: 0.73
• guiApplications=false causes broken systemd environment (#10818), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Shengyis]

WslLogs-2024-08-14_16-21-29.zip

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Detected appx version: 2.2.4.0
Found no WSL traces in the logs

[suiryc]

Probably related to issue #11857
For now systemd v256 needs specific .wslconfig parameters (see #11857 (comment) for details) to start properly, otherwise by default it waits for 30s after boot to actually start and mounts /tmp which breaks X0 among other things.

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!