On Thu Oct 9 13:43:03 2025 +0000, Vasiliy Stelmachenok wrote:
Yes, it looks much better for me, thank you! Quickly tested on AMD / Intel / NVIDIA, seems to work fine. Although in the case of AMD+NVIDIA, it looks that when using EGL implementation from Mesa information about dGPU cannot be obtained correctly, because NVIDIA device is controlled by a closed driver, which leads to these errors:
0144:trace:wgl:init_egl_devices Initializing EGL device 0x55557d6a6db0 libEGL warning: pci id for fd 46: 10de:25a2, driver (null) pci id for fd 47: 10de:25a2, driver (null) pci id for fd 48: 10de:25a2, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 46: 10de:25a2, driver (null) pci id for fd 47: 10de:25a2, driver (null) pci id for fd 48: 10de:25a2, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 46: 10de:25a2, driver (null)This is not critical, it just creates some junk in logs and seems to be the same thing happens for eglinfo, so this is probably not our issue.
Fwiw these messages are being printed when both MESA and NVIDIA EGL libraries are being tried. I could see them as well but now anymore after installing the NVIDIA proprietary package (which I suspect possibly broke the MESA libraries, or bypass them).
In any case it's not something we can do anything about.