Trying to set up an X environment on WSL is a pain, and IME stops working at times for no reason I can figure out. Plus, I don’t actually need a desktop environment in my desktop environment....
Trying to set up an X environment on WSL is a pain, and IME stops working at times for no reason I can figure out. Plus, I don’t actually need a desktop environment in my desktop environment. Being able to just run GUI apps on WSL as regular windowed apps with no complex setup, assuming that is how it’s going to work, will be a welcome change.
Yeah it can be a massive PITA getting things running correctly and keeping them running using a windows WSL supporting X server. However WSL's recently announced GUI support is going to be using...
Yeah it can be a massive PITA getting things running correctly and keeping them running using a windows WSL supporting X server. However WSL's recently announced GUI support is going to be using Wayland, so hopefully X compatibility issues should soon be a thing of the past:
The timing of this thread is amazing, I set this up at work today. It's really not any worse than setting up SSH X connections. In Windows: Install VcXsrv In WSL Run XLaunch from start menu Choose...
The timing of this thread is amazing, I set this up at work today. It's really not any worse than setting up SSH X connections.
Choose a static display number (I like 10, but to each their own)'
Accept defaults on next screen
Disable access control on next (this is temporary)
Launch it, no need to save
In WSL:
sudo apt install x11-apps x11-common x11-utils
xauth generate localhost:10.0
echo"export DISPLAY=localhost:10.0" >> .bashrc
# Copy output from next command to use later
xauth list|awk '{ print "-cookie "$3 }'
Back to Windows:
Exit the X server running in your tray
Run XLaunch again
Use same settings as above, but instead of disabling access control, paste that output as an additional parameter.
Save the configuration file this time before hitting Finish. You can then re-launch X in the future by double-clicking that file with all of those settings.
Back to WSL:
xclock
If that launches a clock, congratulations, my tipsy tutorial worked! It'll work fine for local stuff and any SSH connections if you pass -X.
If I'm reading that post correctly, they're bringing DirectX to regular Linux as well. That's pretty huge deal, although I'm still skeptical of Microsoft's altruism. Given it's a closed-source...
If I'm reading that post correctly, they're bringing DirectX to regular Linux as well. That's pretty huge deal, although I'm still skeptical of Microsoft's altruism. Given it's a closed-source binary they are releasing, they could decide to charge for it at any time.
Trying to set up an X environment on WSL is a pain, and IME stops working at times for no reason I can figure out. Plus, I don’t actually need a desktop environment in my desktop environment. Being able to just run GUI apps on WSL as regular windowed apps with no complex setup, assuming that is how it’s going to work, will be a welcome change.
Yeah it can be a massive PITA getting things running correctly and keeping them running using a windows WSL supporting X server. However WSL's recently announced GUI support is going to be using Wayland, so hopefully X compatibility issues should soon be a thing of the past:
https://devblogs.microsoft.com/commandline/the-windows-subsystem-for-linux-build-2020-summary/
The timing of this thread is amazing, I set this up at work today. It's really not any worse than setting up SSH X connections.
In Windows:
In WSL:
Back to Windows:
Back to WSL:
If that launches a clock, congratulations, my tipsy tutorial worked! It'll work fine for local stuff and any SSH connections if you pass
-X.If I'm reading that post correctly, they're bringing DirectX to regular Linux as well. That's pretty huge deal, although I'm still skeptical of Microsoft's altruism. Given it's a closed-source binary they are releasing, they could decide to charge for it at any time.