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 launch GUI apps since 2.0.12 #11064

Closed
1 of 2 tasks
dciarniello opened this issue Jan 23, 2024 · 3 comments
Closed
1 of 2 tasks

Cannot launch GUI apps since 2.0.12 #11064

dciarniello opened this issue Jan 23, 2024 · 3 comments

Comments

@dciarniello
Copy link

Windows Version

11

WSL Version

2.1.1.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

Since v2.0.12 of WSL, it has not been possible to launch GUI apps without jumping through hoops. This issue was reported here but the issue was moved to WSLg (microsoft/wslg#1156). The issue is not, however, a WSLg issue but a WSL issue as the problem appeared with 2.0.12 which had no WSLg-related changes.
The problem looks to have been introduced with the "fix" to #10818.

microsoft/wslg#1156, amongst others, has the details of the workaround that is required to be able to launch GUI apps.

Expected Behavior

GUI apps start as usual

Actual Behavior

GUI apps do not start

Diagnostic Logs

No response

Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Open similar issues:

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

@OneBlue
Copy link
Collaborator

OneBlue commented Jan 23, 2024

Closing since there is no repro instruction nor error message.

@OneBlue OneBlue closed this as completed Jan 23, 2024
@dciarniello
Copy link
Author

Pointing the to the ticket that does have the repro instructions was not enough? I would have updated this ticket if asked.

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

2 participants