Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FXApp::openDisplay: unable to open display :0 #11879

Closed
1 of 2 tasks
rye2020 opened this issue Aug 4, 2024 · 8 comments
Closed
1 of 2 tasks

FXApp::openDisplay: unable to open display :0 #11879

rye2020 opened this issue Aug 4, 2024 · 8 comments

Comments

@rye2020
Copy link

rye2020 commented Aug 4, 2024

Windows Version

Microsoft Windows [Version 10.0.26120.1330]

WSL Version

WSL version: 2.3.14.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

Linux version 6.6.36.3-microsoft-standard-WSL2 (root@39abeb63c66c) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP PREEMPT_DYNAMIC Sat Jun 29 07:01:04 UTC 2024

Distro Version

Ubuntu 22.04

Other Software

Any GUI app. xfe gives the message. So do many other GUI apps. Some other GUI apps just hang with no message.

Repro Steps

runnin any GUI app

Expected Behavior

none

Actual Behavior

jrm@LY7i:~$ xfe
FXApp::openDisplay: unable to open display :0
JM System Info.txt

Diagnostic Logs

Please see the attached file

Copy link

github-actions bot commented Aug 4, 2024

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 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!

Closed similar issues:

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

@rye2020
Copy link
Author

rye2020 commented Aug 4, 2024

logs are in the attached file

@rye2020
Copy link
Author

rye2020 commented Aug 7, 2024

see syslog data:
image

@OneBlue
Copy link
Collaborator

OneBlue commented Aug 9, 2024

/logs

@rye2020
Copy link
Author

rye2020 commented Aug 10, 2024

Copy link

Diagnostic information
Detected appx version: 2.3.14.0

@EzequielBruni
Copy link

Anyone figure this out? I'm having the same problem.

@rye2020
Copy link
Author

rye2020 commented Aug 17, 2024

problem solved with "sudo do-release-upgrade"

@rye2020 rye2020 closed this as completed Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants