NVIDIA update 580.126.09 crashes xreader

[patrioticprayer]

Distribution

Linux Mint 22.3, X11/Cinnamon

Package version

xreader 4.6.3

Frequency

Always

Bug description

The NVIDIA driver was updated on 2026-04-27 from 580.126.09 to 580.142 and xreader broke right after. The new driver version likely changed how EGL/GBM initialization behaves and xreader is now aborting on startup because of it.

Steps to reproduce

Before a clean isolated install of 580.142, xreader runs fine. After the install, xreader doesn't run at all. When running in terminal, the following error is shown: "Could not create GBM EGL display: EGL_NOT_INITIALIZED. Aborting..."

Expected behavior

xreader should work after updating any NVIDIA driver.

Additional information

GPU: NVIDIA Quadro K620 (GM107GL)
Working driver: 580.126.09-0ubuntu0.24.04.2
Broken driver: 580.142-0ubuntu0.24.04.1
.xsession-errors: No relevant entries

[leigh123linux]

Distribution

Linux Mint 22.3, X11/Cinnamon

Package version

xreader 4.6.3

Frequency

Always

Bug description

The NVIDIA driver was updated on 2026-04-27 from 580.126.09 to 580.142 and xreader broke right after. The new driver version likely changed how EGL/GBM initialization behaves and xreader is now aborting on startup because of it.

The 580 driver is legacy release, it only gets bug fixes and kernel fixes, no new features.

Steps to reproduce

Before a clean isolated install of 580.142, xreader runs fine. After the install, xreader doesn't run at all. When running in terminal, the following error is shown: "Could not create GBM EGL display: EGL_NOT_INITIALIZED. Aborting..."

GBM errors are normally associated with wayland , not xorg.

Expected behavior

xreader should work after updating any NVIDIA driver.

Additional information

GPU: NVIDIA Quadro K620 (GM107GL) Working driver: 580.126.09-0ubuntu0.24.04.2 Broken driver: 580.142-0ubuntu0.24.04.1 .xsession-errors: No relevant entries

Maybe ubuntu have released a broken driver.
Is there any thing in xorg log?

[patrioticprayer]

Unfortunately, a Timeshifted restore wiped out the Xorg log. Software Update now skips the 580.142 version. If I restore to an older snapshot, I could reinstall 580.142 again, crash reader agsin, and get the Xorg log but doesn't the crash message provide everything needed to debug? Everything else seemed to be working fine except the application crash.

…

On Tue, Apr 28, 2026, 1:30 AM Leigh Scott ***@***.***> wrote: *leigh123linux* left a comment (linuxmint/xreader#710) <#710 (comment)> Distribution Linux Mint 22.3, X11/Cinnamon Package version xreader 4.6.3 Frequency Always Bug description The NVIDIA driver was updated on 2026-04-27 from 580.126.09 to 580.142 and xreader broke right after. The new driver version likely changed how EGL/GBM initialization behaves and xreader is now aborting on startup because of it. The 580 driver is legacy release, it only gets bug fixes and kernel fixes, no new features. Steps to reproduce Before a clean isolated install of 580.142, xreader runs fine. After the install, xreader doesn't run at all. When running in terminal, the following error is shown: "Could not create GBM EGL display: EGL_NOT_INITIALIZED. Aborting..." GBM errors are normally associated with wayland , not xorg. Expected behavior xreader should work after updating any NVIDIA driver. Additional information GPU: NVIDIA Quadro K620 (GM107GL) Working driver: 580.126.09-0ubuntu0.24.04.2 Broken driver: 580.142-0ubuntu0.24.04.1 .xsession-errors: No relevant entries Maybe ubuntu have released a broken driver. Is there any thing in xorg log? — Reply to this email directly, view it on GitHub <#710 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNSMYHANDF2PFKSNKP2OFSL4YA6XXAVCNFSM6AAAAACYIW6ZJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGMZSGU4TKMBQHE> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>