![xming wsl xming wsl](https://raw.githubusercontent.com/wiki/goreliu/wsl-terminal/images/wsl-terminal-3.png)
No need to provide specs of the video cards on the client as I am not trying to impress anyone. The remote X display rendering is horribly slow, and it is not due to lack of display/GL/drawing or any other video card hardware capability on the client side.
Xming wsl windows 7#
(for the record, I'm trying to use it to run virt-manager remotely from a Windows 7 system). The mouse works fine elsewhere in Windows but as soon as you place it over any part of the X window, it vanishes, making it useless for myself or more importantly for my wife who I am trying to set remote access to an X/Linux app up for.
Xming wsl software#
There is little to no documentation of anything for this windows X server.Ī major show-stopper for usability of this software for me is the problem of the mouse cursor disappearing while it is over the remote X window/application regardless of which type of launch you do. then it doesn't really matter how awesome the software may be in other ways. The software may be a technical marvel, but if key features/functionality do not work, there is no documentation available on said feature(s), and no answers from the developers for most/all questions posted - some as long as 2-3 years ago. You can read more about the security implications of X11 Forwarding here and elsewhere.As a non-programmer of X display software I cannot judge the code, etc., so I can only really review as a user - ie, ease of use, documentation, etc. You were probably trying to fix stuff and added that, but remove it and try simply using -X/ -Y flag, or configuring for X11 Forwarding for the specific host, or with a flag at runtime. Either way, you will need to enable ForwardX11 on the client, and it is not recommended to do this system-wide for all hosts, but instead selectively for each host.ĭon't mess with DISPLAY and allow your client and the system to set everything up. When you use -X/-Y flag, you're activating ForwardX11 on the client, the same as by setting up a configuration. Now you can run $ ssh theserver and ForwardX11 will be active. You can do this by editing your ~/.ssh/config for the user, and adding a Host entry for your remote server: Host theserver X11Forwarding needs to be enabled on the server, but that doesn't mean it's enforced. You cannot force a client to enable X11Forwarding by putting an entry in any sshd_config file, but instead need to enable ForwardX11 on the client machine, and for ssh not sshd. Again, launching combined commands does yield a fully functional GUI ( ssh -X 10.0.0.168 gvim will create a GVIM window.) Still, I cannot launch any GUI programs after getting into the SSH session.
![xming wsl xming wsl](https://user-images.githubusercontent.com/7049700/83973782-69685b00-a89d-11ea-877f-5e6af7b72838.png)
On the client machine, in ~/.ssh/config, I have set up: host 10.0.0.168 And, I get the following error with connecting first, and then issuing gvim command: Similarly, combining the connection statement with the gvim command gets me a lively Gvim window. They both have set the $DISPLAY variable: In my case, hooking up SSH connections using -X and -Y are identical. I should have opted to show the demo using -X flag.
![xming wsl xming wsl](https://ariya.io/images/2018/06/xming.png)
Yet, after having logged into the Linux Mint machine using ssh -Y address_of_remote_server, I cannot launch any programs that has GUI. I have set a Linux Mint machine to pick up X11Forwarding by specifying the following in /etc/ssh/sshd_config, yet, I have trouble accessing the server using Ubuntu 18.04.1 LTS hosted as WSL on Windows 10.
Xming wsl free#
Then, simply connect to the host using the -X flag and enjoy free access to all GUI programs on the remote machine! This DISPLAY variable shall match with the Xming that runs On the client machine, do specify export DISPLAY=127.0.0.1:0.0 in the.Remote host will try to render GUI on its own display port On the host machine, do not put any DISPLAY= statement there.