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

X Windows broken on fast ring WSL2 (?) #5106

Closed
rwilliams opened this issue Apr 19, 2020 · 7 comments
Closed

X Windows broken on fast ring WSL2 (?) #5106

rwilliams opened this issue Apr 19, 2020 · 7 comments
Labels

Comments

@rwilliams
Copy link

  • Your Windows build number:
    10.0.19608.1006

  • What you're doing and what's happening:
    Attempting to run an x windows app like gitkraken, nautilus, xfce, jetbrains toolbox, etc.
    I get the following error.

(gitkraken:273): Gtk-WARNING **: 05:50:35.385: cannot open display: 192.168.1.2:0.0

I attempted a fresh Ubuntu LTS install as well and received the same error. I don't believe anything has changed on my end except running the Windows update.

  • What's wrong / what should be happening instead:

With either x410/VcXsrv etc I should be able to launch x windows apps. I've been running various windowed apps for several months now on WSL2 without issue.

@rwilliams
Copy link
Author

rwilliams commented Apr 19, 2020

Tested on version 10.0.19603.1000 and it works as expected.

@dseynhae
Copy link

When you started VcXsrv, did you verify it actually created a display on :0 (and no other number)?
Also, if you have a secure connection, you need to use the localhost TCP/IP address:

export DISPLAY=localhost:0.0

I am not sure about WSL 2, it is possible that they use a Unix Socket for secure connections, in which case your environment variable can NOT mention the host name (or its IP address):

export DISPLAY=:0.0

@rwilliams
Copy link
Author

rwilliams commented Apr 20, 2020

@beltaurus On WSL2 I've been using host ip or export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0. Something changed in the new build as it's been working fine for months.

@rwilliams rwilliams changed the title X Windows broken on fast ring (?) X Windows broken on fast ring WSL2 (?) Apr 20, 2020
@therealkenc
Copy link
Collaborator

image

@rwilliams
Copy link
Author

I'll update to 19608 again and try.

@therealkenc
Copy link
Collaborator

One thing to try after you upgrade, assuming your problem persists, is use the ip address your DHCP gave your Windows machine not the one in /etc/resolv.conf. Also take a look at what ip route | grep default | awk '{print $3}' returns (that's your WSL default gateway). That might or might not be the same address you see in /etc/resolv.conf.

@rwilliams
Copy link
Author

Re-installed 19608 and it's working fine with no changes.

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

No branches or pull requests

3 participants