Environment
Windows build number 10.0.19041.746
Ubuntu 20.04
Linux version 4.19.128-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Tue Jun 23 12:58:10 UTC 2020
Steps to reproduce
The error can be reproduced by running any X server related command. I have been using xeyes for troubleshooting
xeyes strace output
Expected behavior
A pair of eyes should open outside of the terminal which follows my mouse. (All other X server programs have a similar error)
Actual behavior
Nothing happens and I get the following error in my terminal:
Error: Can't open display: localhost:0.0
Additional Details
I have tried running Xming and XLaunch/VcXsrv using the -ac flag. I have also attempted to use the X410 X server with the same result.
VcXsrv is system tray: DESKTOP-LN1HSHQ:0.0 - 0 clients
In /etc/ssh/sshd_config I have set X11Forwarding yes X11UseLocalhost yes
I have tried setting DISPLAY to
localhost:0.0
:0.0
127.0.0.1:0.0
$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0 Which is my address from /etc/resolv.conf
As an additional note, setting DISPLAY=$(cat /etc/re....):0 results in an ~30 second delay before the error occurs. All other DISPLAY settings produce the error instantly.
Disabling Windows Defender Firewall had no effect.
Environment
Steps to reproduce
The error can be reproduced by running any X server related command. I have been using
xeyesfor troubleshootingxeyes strace output
Expected behavior
A pair of eyes should open outside of the terminal which follows my mouse. (All other X server programs have a similar error)
Actual behavior
Nothing happens and I get the following error in my terminal:
Error: Can't open display: localhost:0.0Additional Details
I have tried running Xming and XLaunch/VcXsrv using the
-acflag. I have also attempted to use the X410 X server with the same result.VcXsrv is system tray:
DESKTOP-LN1HSHQ:0.0 - 0 clientsIn /etc/ssh/sshd_config I have set
X11Forwarding yesX11UseLocalhost yesI have tried setting DISPLAY to
localhost:0.0:0.0127.0.0.1:0.0$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0Which is my address from /etc/resolv.confAs an additional note, setting DISPLAY=$(cat /etc/re....):0 results in an ~30 second delay before the error occurs. All other DISPLAY settings produce the error instantly.
Disabling Windows Defender Firewall had no effect.