microsoft
Error: Can't open display: :0
Windows Version
10.0.22631.4317
WSL Version
2.3.25.0
Are you using WSL 1 or WSL 2?
- [x] WSL 2
- [ ] WSL 1
Kernel Version
5.15.153.1-microsoft-standard-WSL2
Distro Version
Arch Linux
Other Software
No response
Repro Steps
Try to start a graphical X-program.
Like
dbeaver
or
xeyes
$ xeyes
Error: Can't open display: :0
$ echo $DISPLAY
:0
This used to work.
I recently upgraded to a later WSL version.
This might be the cause of the bug.
Expected Behavior
WSL should start a graphical window.
Actual Behavior
No window is started.
Diagnostic Logs
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1
The script will output the path of the log file once done.
If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here
Once completed please upload the output files to this Github issue.
Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
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!
Open similar issues:
- Cannot open display :0. Installed wsl on W11 and try to start grafical application kstars but say Cannot open display :0 (#12184), similarity score: 0.76
Closed similar issues:
- WSL 2 Error: Can't open display: localhost:0.0 (#6430), similarity score: 0.77
- wslg worked before, now doesn't seem to work. (#11864), similarity score: 0.76
- Error: Can't open display: :0 on Win11 22000 (#9078), similarity score: 0.76
- WSL2 can't open display (#6181), similarity score: 0.76
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
- Have you tried
wsl.exe --shutdown(which will reset WSLg as well) and trying again? - Can you reproduce this in another distro you have installed?
Thank you @sirredbeard for the answer.
For some reason, executing these commands will make GUI applications work again:
sudo umount /tmp/.X11-unix
sudo rm -rf /tmp/.X11-unix
sudo ln -s /mnt/wslg/.X11-unix /tmp/.X11-unix
Since I am using a wsl distro that I exported from a docker container - is this link something new that you have to set in order for wslg to work? (probably baked into the default distros that you can use?)
I could not reproduce it in another distro.
In my debian wsl container GUI applications still work.
That is odd, I haven't experienced that with distros exported from existing Docker or Podman containers. Which one is it, if you don't me asking? Does it have X and related packages already pre-installed?
Hello,
I have similar problem with WSL Ubuntu 24.04 https://askubuntu.com/questions/1536740/wsl-ubuntu-24-04-display-is-not-working
I played around with DISPLAY variable but no way...
miroi@MiroPhenomII-X6:~/.export DISPLAY=:0.0
miroi@MiroPhenomII-X6:~/.xclock
Error: Can't open display: :0.0
miroi@MiroPhenomII-X6:~/.export DISPLAY=localhost:0.0
miroi@MiroPhenomII-X6:~/.xclock
Error: Can't open display: localhost:0.0
miroi@MiroPhenomII-X6:~/.
Log file was attached to this issue.
You're supposed to use collect-wsl-logs.ps1, which the bot gave a link to in "how to collect wsl logs".
