NVIDIA / NVIDIA/open-gpu-kernel-modules

eglSwapBuffers failed with 0x300d; app windows do not render

Open
#784 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
17.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

NVIDIA Open GPU Kernel Modules Version

570.86.16-2

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
  • I confirm that this does not happen with the proprietary driver package.
  • Author Note: I did not have time to swap my setup to the proprietary driver package to test; if someone could try to replicate with the proprietary package, that would be great.
Operating System and Version

Arch Linux

Kernel Release

6.13.2-zen1-1-zen

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
  • I am running on a stable kernel release.
Hardware: GPU

GPU 0: NVIDIA GeForce RTX 4090 (UUID: GPU-0fc352e5-7f1b-7fd6-1d4a-7c06358cbf69)

Describe the bug

Since updating to 570.86.16, a lot of apps are reporting eglSwapBuffers EGL_BAD_SURFACE errors.

This can be easily replicated with krunner. Triggering it once works, but any subsequent launches causes the error and prevents the window from being displayed.

KDE and QT were notified, the consensus seems to be a driver bug.

The issue happened with 565.x as well, but it was intermittent. Now it can be reproduced every single time (thus pointing towards a driver issue).

To Reproduce
  • Open Krunner window
  • Close Krunner window
  • Try to open Krunner window, it will fail to display
Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

Relevant package versions:

egl-wayland 4:1.1.17-1
lib32-nvidia-utils 570.86.16-1
libva-nvidia-driver 0.0.13-1
linux-firmware 20250109.7673dffd-1
linux-zen 6.13.2.zen1-1
nvidia-open-dkms 570.86.16-2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no source file or test. Start by reproducing the failure by opening and closing the Krunner window, then inspect the attached nvidia-bug-report.log.gz and the linked KDE and Qt reports; done means the repeated launch no longer produces EGL_BAD_SURFACE or a missing window.

Written by the indexing model from the issue text.

Assessment

Tech stack
arch-linux, c, linux
Domain
computer-graphics, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.