Can't use X-Server in WSL 2 (continued)

[numeric-lee]

Ben,
I was able to use graphic applications in WSL using XMING and Export DISPLAY=:0.0

However, once I upgraded to WSL2 (needed for docker) the graphic export stopped working.

Things tried:

• downloading VcXsrv
• changing to export DISPLAY=172.28.80.1:0 (my host#)
• switching to another graphics application
• running vcxsrv -ac from bash (command not recognized)
• running vcxsrv -ac from powershell (command not recognized)
• turning firewall off

My Windows 10 build: 19041.1

Here is a typical error message

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-lw' qt.qpa.screen: QXcbConnection:
Could not connect to display :0.0
Could not connect to any X display.

if my display path is anything other than 0.0 I also get

Authorization required, but no authorization protocol specified

In #4106 you advise to run "vcxsrv -ac" from the bash command line and at least one user accepted that as a solution. I downloaded vcxsrv.exe from sourceforge as an .exe outside of bash, and I see no way to execute it from bash

Many thanks

[therealkenc]

Could not connect to display :0.0

Your display is not on :0.0.

/dupe #637 (message), #4106 (message), #4210 (message), LZ #4619.

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

[winest]

Script to solve this problem

[snowman]

see Unable to accessing Windows applications from WSL