Arch Linux

l3gi0n

Member

Registered: 2025-10-05

Posts: 1

wsl: Failed to start the systemd user session for 'l3gi0n'.

running "wsl" in windows terminal sometimes randomly gives the following error:

wsl: Failed to start the systemd user session for 'l3gi0n'. See journalctl for more details.

[l3gi0n@Euler ~]$ journalctl _SYSTEMD_UNIT=user@$(id -u l3gi0n).service
-- Boot fba24d125ac549528199f473c3129ded --
Oct 05 15:21:37 Euler (sd-exec-strv)[221]: '/run/systemd/user-generators/wsl-user-generator' is marked world-writable, which is a security risk as it is executed with privileges. Please remove world writability permission bits. Proceeding anyway.


[l3gi0n@Euler ~]$ ls -l /run/systemd/user-generators/
total 0
lrwxrwxrwx 1 root root 5 Oct  5 15:22 wsl-user-generator -> /init

[l3gi0n@Euler ~]$ systemctl --user --failed
Failed to connect to user scope bus via local transport: No such file or directory
[l3gi0n@Euler ~]$ systemctl --user status
Failed to connect to user scope bus via local transport: No such file or directory
[l3gi0n@Euler ~]$ cat /etc/wsl.conf
[boot]
systemd=true

[user]
default=l3gi0n

[l3gi0n@Euler ~]$ ls -ld /run/user/$(id -u)
drwx------ 2 l3gi0n l3gi0n 40 Oct  5 15:22 /run/user/1000
[l3gi0n@Euler ~]$ systemctl status user@1000.service
× user@1000.service - User Manager for UID 1000
     Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
    Drop-In: /usr/lib/systemd/system/user@.service.d
             └─10-login-barrier.conf
     Active: failed (Result: resources)
 Invocation: a8e1a3bf7bb04c508a425d64d410e21c
       Docs: man:user@.service(5)
   Mem peak: 8.3M
        CPU: 479ms

Last edited by l3gi0n (2025-10-05 22:41:17)

Allan

Pacman

From: Brisbane, AU

Registered: 2007-06-09

Posts: 11,581

Website

Re: wsl: Failed to start the systemd user session for 'l3gi0n'.

This is a re-regression with WSL 2.6.1

https://github.com/microsoft/WSL/issues/13186

---

PGP Key: F99FFE0FEAE999BD | I develop pacman - buy me a drink!