wsldhost: no connection could be made
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 305
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Trying to make this work with the X Server provided by wslg; if possible I'd like to avoid a 3rd-party X Server.
To be able to successfully start wsld, I needed to apply the systemd unit file as described here: https://github.com/nbdd0121/wsld/issues/21#issuecomment-1345530909.
However, all X11 applications fail with Error: Can't open display: :0. Manually starting wsldhost.exe on the Windows side shows this error when wsld tries to connect: Error: No connection could be made because the target machine actively refused it. (os error 10061).
From what I understand, wslhost.exe by default tries to connect to 127.0.01:6000, but netstat doesn't show anything listening on that port. Do I need to use a different port for the WSLg built-in X Server?
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing how wsldhost.exe connects to the WSLg X Server and the systemd unit configuration referenced in issue #21. Check the wslhost.exe connection target against netstat output, including 127.0.0.1:6000. Done means X11 applications start through WSLg without requiring a third-party X Server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100