Arch Linux

BiffenB

Member

Registered: 2024-07-01

Posts: 21

[SOLVED] EGL issue causing programs to fail on start

Hello! I'm having trouble with running certain games through Wine/Proton. Information about my system can be found at the bottom of the post. It only happens with games which use EGL, and I've isolated the issue to my EGL stack ("Device #1" specifically):

$ eglinfo -B
GBM platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 580.126.18
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 580.126.18
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.126.18
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Wayland platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 580.126.18
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 580.126.18
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.126.18
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 580.126.18
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 580.126.18
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.126.18
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 580.126.18
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 580.126.18
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.126.18
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 580.126.18
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 580.126.18
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.126.18
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
libEGL warning: pci id for fd 26: 10de:1b06, driver (null)

pci id for fd 30: 10de:1b06, driver (null)
pci id for fd 31: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 26: 10de:1b06, driver (null)

pci id for fd 30: 10de:1b06, driver (null)
pci id for fd 31: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 26: 10de:1b06, driver (null)

eglinfo: eglInitialize failed

Device #2:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 21.1.8, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 26.0.1-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 21.1.8, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 26.0.1-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 21.1.8, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

I tested xeyes as well as all of the gears-tests in mesa-util's mesa-demos (eglgears_wayland, eglgears_x11, es2gears_wayland, es2gears_x11, glxgears, peglgears, vkgears, xeglgears). All of them work except peglgears:

$ peglgears
libEGL warning: pci id for fd 4: 10de:1b06, driver (null)

pci id for fd 5: 10de:1b06, driver (null)
pci id for fd 6: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
pci id for fd 5: 10de:1b06, driver (null)
pci id for fd 6: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
peglgears: EGL version = 1.5
peglgears: EGL_VENDOR = Mesa Project
38344 frames in 5.0 seconds = 7668.783 FPS

One of the games I’ve tested runs using wine for a couple seconds, before killing all output to the monitor. The errors written to the console are (practically) identical to the ones above. Software GL causes the same issues, but OpenGL over Vulkan via Zink has differing output:

$ env __GLX_VENDOR_LIBRARY_NAME=mesa __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_DRIVER=zink LIBGL_KOPPER_DRI2=1 wine StickFight.exe
011c:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!

After this there is no output, but the process doesn’t terminate either.

I compiled and tested https://github.com/mishima2077/opengl-tests, which all work just fine. The issue seems isolated to EGL, since OpenGL appears fully functional. Strangely, glmark2-egl (which appears to use Xwayland) ran fine as well, the only non-wine-based executable that has failed on me is peglgears.

I believe my issue might be similar to that in this topic. Unfortunately, the steps in the thread haven’t led me to any particular conclusion. I’ve tried running blobby with/without X11 as well (and both succeed).

System information:
OS: Arch x86_64
Kernel: Linux 6.18.13-arch1-1
DE: KDE Plasma 6.6.1
WM: KWin (Wayland)
CPU: AMD Ryzen 7 1800X (16) @ 3.60 GHz
GPU: NVIDIA GeForce GTX 1080 Ti [Discrete]

$ pacman -Q | grep nvidia
linux-firmware-nvidia 20260221-1
nvidia-580xx-dkms 580.126.18-2
nvidia-580xx-utils 580.126.18-2
opencl-nvidia-580xx 580.126.18-2

$ pacman -Q | grep mesa
lib32-mesa 1:26.0.1-1
lib32-vulkan-mesa-implicit-layers 1:26.0.1-1
mesa 1:26.0.1-1
mesa-utils 9.0.0-7
vulkan-mesa-implicit-layers 1:26.0.1-1

$ pacman -Q | grep egl
egl-gbm 1.1.3-1
egl-wayland 4:1.1.21-1
egl-x11 1.0.4-1
eglexternalplatform 1.2.1-1
freeglut 3.8.0-1 ###unrelated package###
gegl 0.4.66-2 ###unrelated package###

No output from “$ pacman -Q | grep nouveau”.

I’d appreciate any assistance I could get, so if anyone has some ideas, please let me know!

Last edited by BiffenB (2026-03-02 18:46:59)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 73,365

Re: [SOLVED] EGL issue causing programs to fail on start

All of them work except peglgears … Strangely, glmark2-egl (which appears to use Xwayland) ran fine as well, the only non-wine-based executable that has failed on me is peglgears

Software GL causes the same issues

Can you run notepad.exe ?

Edit: fwwi, the "libEGL warning: egl: failed to create dri2 screen" is noise, that's very unlikely your problem (as evidenced by all main egl clients running fine - I've no idea what the problem w/ peglgears would be)

Last edited by seth (2026-03-02 15:22:57)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

BiffenB

Member

Registered: 2024-07-01

Posts: 21

Re: [SOLVED] EGL issue causing programs to fail on start

$ wine notepad.exe 
01a0:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 000000014002ED28, 39) stub
01a0:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!

After which it simply hangs.

Sorry, took me a minute to get a hold of notepad.exe.

BiffenB

Member

Registered: 2024-07-01

Posts: 21

Re: [SOLVED] EGL issue causing programs to fail on start

Got the following output with a new wine prefix:

$ WINEPREFIX=~/wine-test wine winecfg
wine: created the configuration directory '/home/(USERNAME)/wine-test'
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
004c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0054:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
libEGL warning: pci id for fd 33: 10de:1b06, driver (null)

pci id for fd 34: 10de:1b06, driver (null)
pci id for fd 35: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 33: 10de:1b06, driver (null)

pci id for fd 34: 10de:1b06, driver (null)
pci id for fd 35: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 33: 10de:1b06, driver (null)

libEGL warning: pci id for fd 33: 10de:1b06, driver (null)

pci id for fd 34: 10de:1b06, driver (null)
pci id for fd 35: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 33: 10de:1b06, driver (null)

pci id for fd 34: 10de:1b06, driver (null)
pci id for fd 35: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 33: 10de:1b06, driver (null)

004c:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
004c:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
004c:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0054:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
0054:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
0054:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0054:err:ole:start_rpcss Failed to open RpcSs service
009c:fixme:file:NtLockFile I/O completion on lock not implemented yet
009c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
00a4:fixme:file:NtLockFile I/O completion on lock not implemented yet
00a4:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
00a4:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5)
00a4:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5)
009c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
009c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
0108:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10
002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10
012c:err:setupapi:do_file_copyW Unsupported style(s) 0x10
012c:err:setupapi:do_file_copyW Unsupported style(s) 0x10
002c:err:setupapi:do_file_copyW Unsupported style(s) 0x10
012c:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:fixme:wineusb:query_id Unhandled ID query type 0x5.

notepad.exe had the exact same output within the new wine prefix.

EDIT: Reinstalled wine (wine-11.3-1), same issues.

Last edited by BiffenB (2026-03-02 16:06:23)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 73,365

Re: [SOLVED] EGL issue causing programs to fail on start

Does it work in an X11 session?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

BiffenB

Member

Registered: 2024-07-01

Posts: 21

Re: [SOLVED] EGL issue causing programs to fail on start

In my login/logout screen, I cannot select an X11 session (and I believe I don't have the prerequisites installed - I'm just running Plasma via Wayland).

$ echo $XDG_SESSION_TYPE
wayland
$ env WINEPREFIX=~/wine-test SDL_VIDEODRIVER=x11 wine notepad.exe 
libEGL warning: pci id for fd 33: 10de:1b06, driver (null)

pci id for fd 34: 10de:1b06, driver (null)
pci id for fd 35: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 33: 10de:1b06, driver (null)

pci id for fd 34: 10de:1b06, driver (null)
pci id for fd 35: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 33: 10de:1b06, driver (null)

00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
0024:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 000000014002ED28, 39) stub
0024:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!

This time it crashed at the end, instead of hanging.

EDIT: In fact, now it crashes every time, regardless of if I set the environment variables or not (with a new terminal and even manually setting the old wine prefix as well).

Last edited by BiffenB (2026-03-02 16:34:09)

tekstryder

Member

Registered: 2013-02-14

Posts: 504

Re: [SOLVED] EGL issue causing programs to fail on start

the "libEGL warning: egl: failed to create dri2 screen" is noise

pci id for fd 30: 10de:1b06, driver (null)
pci id for fd 31: 10de:1b06, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 26: 10de:1b06, driver (null)

@BiffenB for more info on these innocuous warnings please see mesa issues:

• https://gitlab.freedesktop.org/mesa/mesa/-/issues/13684 (actual issue fixed/closed)

and followup about the noise:

• https://gitlab.freedesktop.org/mesa/mesa/-/issues/14206

However the mesa folks aren't in any hurry to accommodate proprietary Nvidia users, particularly when it comes to non-breaking issues.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,064

Re: [SOLVED] EGL issue causing programs to fail on start

FWIW while this "shouldn't™️" be a problem with modern wine anymore, it might still very much affect proton, is that you're lacking lib32-nvidia-580xx-utils you probably want that.

BiffenB

Member

Registered: 2024-07-01

Posts: 21

Re: [SOLVED] EGL issue causing programs to fail on start

I see you experienced something similar a while back with older drivers (and an older version of mesa). I'd honestly prefer to run the nouveau drivers, but I tried, quite unsuccessfully, to switch recently (and just now, requiring me to recover with a bootable usb, but that'll be a story for another thread...). I'll give it another shot tomorrow, so thanks for the heads up! Can I mark the thread as closed somehow, or should it just be left open since it's technically unsolved?

BiffenB

Member

Registered: 2024-07-01

Posts: 21

Re: [SOLVED] EGL issue causing programs to fail on start

FWIW while this "shouldn't™️" be a problem with modern wine anymore, it might still very much affect proton, is that you're lacking lib32-nvidia-580xx-utils you probably want that.

Notepad.exe and peglgears still fail (for new not-so-exciting reasons), but all games I've tested via proton suddenly succeed. I personally have had a good time using open-source alternatives to notepad, so I'll call this a success. eglinfo -b no longer reports any errors either, so it really seems that whatever "shouldn't™️" happen actually did...

Huge thanks to everyone who helped out! And thanks again, Seth!