Comment by Anarch157a
8 hours ago
That's because WSL2 implements an X11 client and sets the DISPLAY variable. X11 network transparency does the rest. You can do the same on Linux, as long as you're to learn how X11 arcane permission system works.
8 hours ago
That's because WSL2 implements an X11 client and sets the DISPLAY variable. X11 network transparency does the rest. You can do the same on Linux, as long as you're to learn how X11 arcane permission system works.
The current architecture is wayland based, with weston and an RDP backend, and the Windows host running an RDP client. X11 apps run on Xwayland within WSL2, so ultimately rendered on the same RDP client.
Windows implements and X11 _server_ (the client in X11 jargon is the app, which if remote works on a remote server - yeah it's confusing. You can have the X11 server on a thin client showing data from an X11 client running on a remote server). They also added Wayland support, too.
`xhost +`
Problem solved