These steps have been tested on Windows 10 with WSL2 running Ubuntu.
First install the dependencies:
apt install mesa-utils libglu1-mesa-dev freeglut3-dev mesa-common-dev
There are more than we need, but also include GLut and Glu libraries to link aginst during compilation for application development (these can be removed if that functionality is not required).
Then, you will need to setup a window server. Windows 11 should have this built in and work out of the box (skip to step 3). In Windows 10 you will need to install one VcXsrv is a popular option (also known as XLaunch).
Once installed, then you will need to make a configuration. You want the following settings:
- First Screen: Multi-Window, Display=0
- Second Screen: Start No Client
- Third Screen: Clipboard=True, Primary Selection=True, Native OpenGL=False, Disable Access Control=True
I recomend you save your configuration file somewhere so that each time you start you window server you can open it instead of rebuilding it. Then start your window server.
Once you have setup and started your Window server, you need to tell Ubuntu/WSL where your display is, we can do this by running the following command:
export DISPLAY=$(awk '/nameserver / {print $2; exit}' /etc/resolv.conf 2>/dev/null):0
export LIBGL_ALWAYS_INDIRECT=0
You will need to do this for every new shell you open. Alternatively, you can add this to your .bashrc
file to have your shell do it for you an start up.
After the following configuration you should be able to run the test application below and see some multi-colored gears spinning:
glxgears
I'm encountering the exact same issue on Windows 11 with WSL2. Upon running glxgears, the native Windows Server for Windows 11 launches, but it only displays a black screen. Whilst the terminal outputs values like "frames in 5.0 seconds," there's no actual visual output. I decided to test VcXsrv to see if it would yield different results, but unfortunately, the same problem persists - this time with an even worse frame rate for the black screen.
Comments suggest that this could potentially stem from a driver problem, given that a window does appear, or that it might be related to window manager settings. However, I'm unsure how to address these concerns within the built-in Windows 11 Windows Server.
Does anyone have any suggestions or recommendations for troubleshooting this?