xorg-server | XQuartz development branches of https | Build Tool library

You need an X11 server. The first Google result for "WSL X11" is https://virtualizationreview.com/articles/2017/02/08/graphical-programs-on-windows-subsystem-on-linux.aspx which says:

To use WSL with graphical programs, an X server will need to be installed on the Windows 10 system and the DISPLAY variable will need to be set in Bash. Fortunately, there are many X servers that run on Windows; some of the more popular free ones are Xming, Cygwin X, and vcXsrv.

The article above also contains some more instructions on how to start an X11 server and to test that it works.

See this gist. Just put your logging mechanism inside the handle_change function and it should work, as tested on an Arch Linux - dwm system.

For archival purposes, here I include the code. All credit goes to Stephan Sokolow (sskolow) on GitHub.

I was able to figure this out -- hopefully it helps someone else:

Step 1: Enable X11 forwarding on the server that hosting the Docker container

1. Make sure /etc/ssh/sshd_config contains the following line:

You must allow anybody to start X11:

Based on issue Karma 1.6 breaks Headless support for Chrome created on github, it is related to the slower machine and happens, because it took > 60 seconds before test bundle was parsed and executed by Chrome and therefore test run was started and communicated back to Karma server. Reasons why it may take long vary.

There are 2 ways to handle timeout:

Investigate why your test bundle loads >60 seconds and make sure it loads faster.

1. Increase browserNoActivityTimeout to highter value, so test bundle has enough time to load.
2. This particular appearance of timeout does not seem to be a Karma issue, but rather problem in the project or misconfiguration.

Based on the Derek's comment

There was a connection that was disconnecting too soon.

He found that in /static/karma.js, when the socket was created, there was a timeout value that is hardcoded to 2 seconds (see below). He just added another 0 to make it 20 seconds and the connection stayed open long enough for the server to respond to the initial request. karma/client/main.js

Lines 14 to 20 in e79463b

I solved my problem, I change the color depth at the launch of Xorg with :

At present there is no GPU installed on any of the VMs and having a graphical desktop on them is not so straight forward. There is a GPU feature request which you can follow by pressing on the star on Public Issue Tracker (PIT) link.

To be able to have and use a graphical desktop you can configure VNC remote access for your VM as described in the URL links 2 and/or 3.

Keep in mind that although above link 2 or 3 steps seem to have succeeded, these are third-party websites containing information that isn’t provided by Google and its contents cannot be guaranteed. Also since there is no GPU installed, this installation might fail for high resolution desktop.

So I finally got this to work. And it seems it was pretty simple. I am not certain how this actually fixes the issue, but now the containers work.

How I fixed it was opening up XQuartz and then opening up the "Terminal" app from the "Applications" menu. Then running the command export DISPLAY=192.168.1.X:0, then xhost +. It outputted something like this "access control disabled, clients can connect from any host". After that I was able to run my docker run commands to launch the desired GUI containers.

I am still uncertain how this works and not running them from my laptops Terminal app, but it worked. It must be something I have set in my local env. Hopefully this helps someone else out who may be running into the same issues.

I tried this steps:

Add to file /etc/modules-load.d/fbtft.conf