systemd user instance does not work in 2.5.x and 2.6.x with RedHat
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Windows Version
Microsoft Windows [Version 10.0.26200.7462]
WSL Version
2.5.10
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
6.6.87.2-microsoft-standard-WSL2
Distro Version
RedHat 9.7
Other Software
No response
Repro Steps
I'm still having the same problem like others before where they go with 2.5.x.
I tried several WSL versions, jumping between 2.4 and 2.6. 2.4 was fine as I remember, but nothing really works since 2.5.x.
- systemctl --user status errors out
- /run/user/1000/bus missing
- podman complains
- systemctl restart user@1000 doesn't help
- disabling wslg has no effect
- I don't see the double mount of /run/user/1000 in any WSL release
The symptoms are the same like in all earlier posts.
Ubuntu 24 seem to work with regard to systemctl --user
I have the same problems with RH9 and RH10.
I have to avoid 6.x now because that breaks podman. At least the 5.x is working so-so with the above problems.
I don't remember any of those problems in 4.x.
Expected Behavior
Have proper user session , dbus
Actual Behavior
No user session and bus
Errors in journalctl:
pam_systemd(sudo:session): Failed to connect to system bus: No such file
Diagnostic Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce on WSL 2.5.10 or 2.6 with RedHat 9.7 using systemctl --user status, and inspect /run/user/1000/bus plus the reported journalctl error. Compare the behavior with WSL 2.4 and Ubuntu 24. Done means a proper user session and dbus are available without the listed errors, and podman no longer fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100