I recently migrated to Windows from MacOS and have found the following paid apps really helpful: 1. [Pengwin]( https://www.whitewaterfoundry.com/ ) - a customized Debian distribution with helpful scripts for setting up a dev environment 2. [X410]( https://x410.dev/ ) - a customized X11 Server They made all the setup really easy. I reuse some of the scripts from Penguin in the Ubuntu distribution. One caveat for those…
GWSL: Run graphical Linux apps in WSL
11–20 of 132 posts
Re: GWSL: Run graphical Linux apps in WSL
#12I recently migrated to Windows from MacOS and have found the following paid apps really helpful: 1. [Pengwin]( https://www.whitewaterfoundry.com/ ) - a customized Debian distribution with helpful scripts for setting up a dev environment 2. [X410]( https://x410.dev/ ) - a customized X11 Server They made all the setup really easy. I reuse some of the scripts from Penguin in the Ubuntu distribution. One caveat for those…
I have not experienced WSL2 a not starting issue at all and I use it every day this year.
Also what benefit does Pengwin have apart from X server? I use the Ubuntu image and I've had no issues.
Re: GWSL: Run graphical Linux apps in WSL
#13I recently migrated to Windows from MacOS and have found the following paid apps really helpful: 1. [Pengwin]( https://www.whitewaterfoundry.com/ ) - a customized Debian distribution with helpful scripts for setting up a dev environment 2. [X410]( https://x410.dev/ ) - a customized X11 Server They made all the setup really easy. I reuse some of the scripts from Penguin in the Ubuntu distribution. One caveat for those…
Is the instability related to one of the above apps? I've been using WSL2 for at least six months without that issue.
I blame it on being on the Dev release channel.
To be honest I thought I had to be on the latest and greatest to take benefit of WSL2.
Re: GWSL: Run graphical Linux apps in WSL
#14Re: GWSL: Run graphical Linux apps in WSL
#15I recently migrated to Windows from MacOS and have found the following paid apps really helpful: 1. [Pengwin]( https://www.whitewaterfoundry.com/ ) - a customized Debian distribution with helpful scripts for setting up a dev environment 2. [X410]( https://x410.dev/ ) - a customized X11 Server They made all the setup really easy. I reuse some of the scripts from Penguin in the Ubuntu distribution. One caveat for those…
WSL2 became available outside of insider builds in version 1903 which came out May 2019. I have not experienced WSL2 a not starting issue at all and I use it every day this year. Also what benefit does Pengwin have apart from X server? I use the Ubuntu image and I've had no issues.
For instance I had a small issue with the scale of the applications. In Windows I have 250% (recommended) scaling applied.
``` export QT_SCALE_FACTOR=2.5
export GDK_SCALE=$(echo "(${QT_SCALE_FACTOR} + 0.49) / 1" | bc) #Round ```
Re: GWSL: Run graphical Linux apps in WSL
#16VcXsrv and a bashrc to set DISPLAY= automatically did it for me export DISPLAY=$(route -n | grep UG | head -n1 | awk '{print $2}'):0 and on the Windows side, start VcXsrv with the 'Disable Access Control' combo box checked. this will enable X clients from other hosts (WSL is another host, basically) to connect to the server without too much hassle. that's it.
This was terrible advice back in the 90s and still is. An attacker anywhere on the network can listen to your input devices, insert fake keypresses, view your screen, etc. Basically a total system compromise.
All without log entries.
The correct way to do this is to use MIT-MAGIC-COOKIE.
One the client host:
$ xauth -extract - $DISPLAY
Then copy the output.
On the host running the X server: $ xauth nmerge -
then paste the output copied previously.
Press enter and CTRL-D (EOF).
If you then check the output of "xhost" on the client, it should only say "Access control enabled."Re: GWSL: Run graphical Linux apps in WSL
#17Re: GWSL: Run graphical Linux apps in WSL
#18VcXsrv and a bashrc to set DISPLAY= automatically did it for me export DISPLAY=$(route -n | grep UG | head -n1 | awk '{print $2}'):0 and on the Windows side, start VcXsrv with the 'Disable Access Control' combo box checked. this will enable X clients from other hosts (WSL is another host, basically) to connect to the server without too much hassle. that's it.
> Disable Access Control This was terrible advice back in the 90s and still is. An attacker anywhere on the network can listen to your input devices, insert fake keypresses, view your screen, etc. Basically a total system compromise. All without log entries. The correct way to do this is to use MIT-MAGIC-COOKIE. One the client host: $ xauth -extract - $DISPLAY Then copy the output. On the host running the X server: $…
Re: GWSL: Run graphical Linux apps in WSL
#19VcXsrv and a bashrc to set DISPLAY= automatically did it for me export DISPLAY=$(route -n | grep UG | head -n1 | awk '{print $2}'):0 and on the Windows side, start VcXsrv with the 'Disable Access Control' combo box checked. this will enable X clients from other hosts (WSL is another host, basically) to connect to the server without too much hassle. that's it.
> Disable Access Control This was terrible advice back in the 90s and still is. An attacker anywhere on the network can listen to your input devices, insert fake keypresses, view your screen, etc. Basically a total system compromise. All without log entries. The correct way to do this is to use MIT-MAGIC-COOKIE. One the client host: $ xauth -extract - $DISPLAY Then copy the output. On the host running the X server: $…
Re: GWSL: Run graphical Linux apps in WSL
#20Anyone have experience with this? The only thing I miss from a Linux Desktop is https://sw.kovidgoyal.net/kitty/ but it requires direct access to GPU as I understand. Anyone tried kitty with this?