microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.46k stars 821 forks source link

Xlib: missing extension "XFree86-VidModeExtension" after upgrade to 16.04 #1885

Closed trzecieu closed 7 years ago

trzecieu commented 7 years ago

Please use the following bug reporting template to help produce actionable and reproducible issues. Please try to ensure that the reproduction is minimal so that the team can go through more bugs!

In order to fix this problem I've tried as follow:

piotr@DZIK:/$ cat /etc/X11/xorg.conf
Section "Module"
        Load "extmod"
EndSection

But it didn't help.

My project uses: XF86VidModeQueryVersion, XF86VidModeGetAllModeLines

See our contributing instructions for assistance.

aseering commented 7 years ago

Hi @asRIA -- so, WSL by itself is text-mode only. While it's true that the functions that you listed above aren't implemented in stock WSL, that's because WSL itself doesn't implement any X functions :-)

My guess is that you installed a third-party X server such as VcXsrv or Xming a while ago, and configured WSL to use it to handle X Windows calls. That third-party server is what needs to support these features. Note that these third-party X servers are Windows applications; you'll have to find and edit their config files on the Windows side.

trzecieu commented 7 years ago

Thank you @aseering for a good answer for it. You were right :)


Update: Just for the others to clarify what's wrong: in 14.04 XF86VidModeGetAllModeLines doesn't work also. Error was placed in my code, where I didn't check if returned number of modes isn't 0. (Yeapp). And I copied the first mode into stack value. For 14.04 it copies some garbage, but in general no exception is thrown. In 16.04 I'm getting memory access validation, and my application crashes.

In both cases I'm having log Xlib: extension "XFree86-VidModeExtension" missing on display ":0.0". But because in 16.04 it was the first and last log what I saw, I thought that this is a reason of my problem.