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

Cannot open GUI apps #12425

Closed
HarryK4673 opened this issue Jan 1, 2025 · 2 comments
Closed

Cannot open GUI apps #12425

HarryK4673 opened this issue Jan 1, 2025 · 2 comments

Comments

@HarryK4673
Copy link

Hi everyone!

I followed the steps and installed those apps. But I can open none of them, such as:

(base) harry@wsl:~$ xcalc
Error: Can't open display: 10.255.255.254:0.0
(base) harry@wsl:~$ vlc
VLC media player 3.0.20 Vetinari (revision 3.0.20-0-g6f0d0ab126b)
[00005565d4ae32d0] main interface error: no suitable interface module
[00005565d4a31220] main libvlc error: interface "globalhotkeys,none" initialization failed
[00005565d4a31220] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[00005565d4ae32d0] skins2 interface error: cannot initialize OSFactory
[00005565d4ac80a0] main playlist: playlist is empty
[00005565d4ae32d0] [cli] lua interface: Listening on host "*console".
VLC media player 3.0.20 Vetinari
Command Line Interface initialized. Type `help' for help.
> ^C[00005565d4ae32d0] [cli] lua interface error: Error loading script /usr/lib/x86_64-linux-gnu/vlc/lua/intf/cli.luac: lua/intf/modules/host.lua:286: Interrupted.
(base) harry@wsl:~$ google-chrome
[4496:4496:0102/005256.263622:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
[4496:4496:0102/005256.264170:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.

Here's my system info:

WSL version: 2.3.24.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4460
Copy link

github-actions bot commented Jan 1, 2025

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:

Closed similar issues:

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

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant