microsoft / wslg

Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
MIT License
9.9k stars 296 forks source link

xserver crashing too fast #1240

Open NickCondron opened 2 months ago

NickCondron commented 2 months ago

Windows build number:

22631.3447

Your Distribution version:

5.15.146.1-microsoft-standard-WSL2 (arch)

Your WSL versions:

WSL version: 2.1.5.0 Kernel version: 5.15.146.1-2 WSLg version: 1.0.60 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.3447

Steps to reproduce:

  1. Run wsl --shutdown
  2. Run wsl distro
  3. Run ls /tmp/.X11-unix
  4. No X0 socket indicating the xserver is not running properly

Following instructions from here: https://github.com/microsoft/wslg/wiki/Diagnosing-%22cannot-open-display%22-type-issues-with-WSLg

$ cat /mnt/wslg/versions.txt
WSLg ( x86_64 ): 1.0.60+Branch.main.Sha.057f5e2e8882b9fb8ec2cb8ef29f16f4fa45760d
Built at: Mon Jan 8 19:07:19 UTC 2024
Mariner: VERSION="2.0.20231130"
DirectX-Headers:
mesa:
pulseaudio: 6f045ff0dca233a939a2aba815f84d177e294122
FreeRDP: c4030980b29322a9cb2190711a5fadeeeb8b6a33
weston: f227edd681479ec3cb2290a25d84d2d3462aebfa

WSL logs:

weston.log

WSL dumps:

No response

Expected behavior:

No response

Actual behavior:

The server socket file does not exist and the /tmp/ directories and links aren't set up.

Running program like xterm gives result: xterm: Xt error: Can't open display: :0

weston.log file contains line: xserver crashing too fast: 134