wslg not available on Arch Linux (systemd 256.6, cgroups v2 enabled)

[here-abarany]

Windows Version

Microsoft Windows [Version 10.0.19045.4894]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Arch Linux

Other Software

WSLg version: 1.0.61
systemd version: 256.6

Repro Steps

1. Install Arch Linux from the Microsoft store.
2. Enable cgroups v2 with kernelCommandLine = cgroup_no_v1=all systemd.unified_cgroup_hierarchy=1 in .wslconfig. (without this systemd fails to function properly)
3. Install gvim (sudo pacman -S gvim)
4. Attempt to run gvim.
5. Check for the presence of /tmp/.X11-unix and /run/user/1000/wayland-0

Expected Behavior

/tmp/.X11-unix and /run/user/1000/wayland-0 are present and gvim opens a GUI window.

Actual Behavior

/tmp/.X11-unix and /run/user/1000/wayland-0 are not present and gvim falls back to editing in the console as it could not connect to the display.

Diagnostic Logs

WslLogs-2024-10-02_16-02-08.zip
debugConsole.log

wslg logs:
wlog.log
stderr.log
weston.log

[github-actions]

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:

• WSL2 + WSLg + systemd support Conflict (#9257), similarity score: 0.75
• guiApplications=false causes broken systemd environment (#10818), similarity score: 0.75
• WSLG Not Running (#9735), similarity score: 0.74
• wsl --version & WSLg not working on WSL2 1.0 on Win10 22H2; empty /mnt/wsl; missing /tmp/.X11 (#9205), similarity score: 0.73
• GUI applications no longer display after enabling systemd (#8896), similarity score: 0.73

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

Diagnostic information

.wslconfig found
	Custom kernel command line found: 'cgroup_no_v1=all systemd.unified_cgroup_hierarchy=1'
Detected appx version: 2.2.4.0

[here-abarany]

I have verified that this is still an issue with the latest 2.3.26 release with WSLg 1.0.65.