oukenn commented 1 day ago

Windows Version

Windows Feature Experience Pack 1000.19060.1000.0

WSL Version

2.3.24.0

Are you using WSL 1 or WSL 2?

[x] WSL 2
[ ] WSL 1

Kernel Version

Linux version 5.15.153.1-microsoft-standard-WSL2 (root@941d701f84f1) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Fri Mar 29 23:14:13 UTC 2024

Distro Version

Ubuntu 22.04

Other Software

xcrysden 1.6.2

Repro Steps

install Xcrysden and use xcrysden command

Expected Behavior

show the Xcrysden

Actual Behavior

xcrysden_log.txt

Diagnostic Logs

tryqe@DESKTOP-QUGPKA7:~/NLZO$ cat /mnt/wslg/versions.txt
WSLg ( x86_64 ): 1.0.65+Branch.main.Sha.25d8697d5049e1994baa6ba542f507347b608ad4
Built at: Wed Aug 14 21:11:14 UTC 2024
Mariner: VERSION="2.0.20240609"
DirectX-Headers:
mesa:
pulseaudio: 6f045ff0dca233a939a2aba815f84d177e294122
FreeRDP: c4030980b29322a9cb2190711a5fadeeeb8b6a33
weston: f227edd681479ec3cb2290a25d84d2d3462aebfa tryqe@DESKTOP-QUGPKA7:~/NLZO$ echo $DISPLAY
:0
tryqe@DESKTOP-QUGPKA7:~/NLZO$ ls -la /tmp/.X11-unix
total 4
drwxrwxrwx 2 root root 40 Nov 11 14:00 .
drwxrwxrwt 10 root root 4096 Nov 13 16:27 . weston.log

github-actions[bot] commented 1 day ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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.71

Closed similar issues:

Error: Can't open display: :0 on Win11 22000 (#9078), similarity score: 0.74
WSL2 can't open display (#6181), similarity score: 0.71

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