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

Debian 12 (bookworm) - GUI not working #12120

Closed
1 of 2 tasks
neskoc opened this issue Oct 3, 2024 · 2 comments
Closed
1 of 2 tasks

Debian 12 (bookworm) - GUI not working #12120

neskoc opened this issue Oct 3, 2024 · 2 comments

Comments

@neskoc
Copy link

neskoc commented Oct 3, 2024

Windows Version

Windows 11 10.0.26100.1742

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Debian 12

Other Software

bless
thunar

Repro Steps

sudo apt install bless
`➜ ~ bless

(bless:42): Gtk-WARNING **: 10:48:47.472: cannot open display:`

'➜ ~ thunar
thunar: Failed to initialize Xfconf: Cannot autolaunch D-Bus without X11 $DISPLAY

(thunar:2202): Gtk-WARNING **: 11:12:37.522: cannot open display:'

Expected Behavior

To run in GUI.
According to the Microsoft wsl tutorial I should not be forced to do any special X-related configuration as some older tutorial suggest.

Actual Behavior

`➜ ~ bless

(bless:42): Gtk-WARNING **: 10:48:47.472: cannot open display:`

'➜ ~ thunar
thunar: Failed to initialize Xfconf: Cannot autolaunch D-Bus without X11 $DISPLAY

(thunar:2202): Gtk-WARNING **: 11:12:37.522: cannot open display:'

Diagnostic Logs

No response

Copy link

github-actions bot commented Oct 3, 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 [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!

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