Id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eatĠx023 24 tc 0 32 0 r y. Visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav Still fails with glxCreateContext but glxinfo -i provides this information: I've installed the WSLg recommended drivers for both Nvidia and Intel Sudo add-apt-repository ppa:kisak/kisak-mesa Also ran $sudo apt install mesa (no effect) Use 'sudo apt autoremove' to remove them.Ġ upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Libxcb-shape0-dev libxcb-sync-dev libxcb-xfixes0-dev libxshmfence-dev libxxf86vm-dev x11proto-xf86vidmode-dev Libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-present-dev libxcb-randr0-dev The following packages were automatically installed and are no longer required: Mesa-common-dev is already the newest version (21.1.3 kisak1b). Libgl1-mesa-dev is already the newest version (21.1.3 kisak1b). Libglu1-mesa-dev is already the newest version (9.0.0-2.1build1). Sudo apt-get install mesa-common-dev libgl1-mesa-dev libglu1-mesa-dev Minor opcode of failed request: 24 (X_GLXCreateNewContext)Ĭurrent serial number in output stream: 59 Major opcode of failed request: 148 (GLX)
X Error of failed request: BadValue (integer parameter out of range for operation) Powershell wsl -update then wsl -shutdown.Your WSLg version: Windows Subsystem for Linux WSLg Preview 1.0.22 Your Distribution version: **Ubuntu 18.04** Windows build number: Win32NT 0.0 Microsoft Windows NT 0.0 Windows 10 Pro Eval copy Build _release.210521-1658 In this case it's model number WD19TB running the latest firmware Expected behavior In fact the laptop has no external monitor HDMI ports and the only way to use a display other than the laptop's built-in panel is to use an Dell docking station. The Intel driver supports two Full Display Devices but the display connectors are on a thunderbolt docking station, not directly connected to the laptop. The nvidia driver is operating as a Render-Only Display Deviceģ. The Nvidia driver is WDDM 3.0 driver and the Intel drivers are WDDM 2.8 so there's a possible mismatch of functionalityĢ. I think the problem has to do with one of these:ġ. Other developers that have a single GPU and where all monitors are directly connected to internal HDMI or DP ports seem to have no problem with GLX apps.
On my Dell laptop, I have a USB-C docking station with two displays attached. All OpenGL (mesa) apps fail when trying to create an OpenGL context.
0 kommentar(er)
