NVIDIA / NVIDIA/open-gpu-kernel-modules
Plasma 6 Wayland black screen: Xid 69 and GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT in kwin_wayland
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
NVIDIA Open GPU Kernel Modules Version
590.48.01
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.
Operating System and Version
CachyOS
Kernel Release
6.18.6-1-cachyos-bore
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 3070 (UUID: GPU-d569c2e4-25de-9e37-ba25-fe632b19dbd0)
Describe the bug
Disclaimer: I've compiled this bug report with the help of ChatGPT.
For some weeks I am experiencing reproducible black screen freezes on KDE Plasma 6 (Wayland) when using the NVIDIA Open Kernel Module driver.
The problem manifests in two closely related failure modes:
Hard GPU error with Xid 69 in kwin_wayland
Silent rendering failure with GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT
Both result in a complete black screen while the system remains running.
The issue is triggered by GPU-accelerated workloads such as Darktable (OpenCL/EGL heavy usage) and Firefox (WebRender / tab creation).
Failure Mode 1 – Xid 69 / EGL context collapse (Darktable)
This failure occurred during GPU-heavy usage in Darktable.
Relevant kernel and compositor logs:
NVRM: Xid (PCI:0000:2b:00): 69, pid=1256, name=kwin_wayland, Class Error: channel 0x00000057, Class 0000c797, Offset 00000d40, Data 00000001, ErrorCode 00000004
Followed immediately by complete EGL / QRhi context collapse in KWin:
kwin_wayland: QRhiGles2: Context is lost
kwin_wayland: Failed to create RHI (backend 2)
kwin_wayland: QQuickRenderControl: Failed to initialize QRhi
kwin_wayland: Could not make egl context current! EGL_BAD_CONTEXT
kwin_wayland: EglGbmLayerSurface::renderTestBuffer: failed to make opengl context current
kwin_wayland: Could not delete framebuffer because no context is current
kwin_wayland: Could not delete texture because no context is current
After this, the screen turned permanently black and the session became unusable.
Failure Mode 2 – Silent framebuffer failure (Firefox)
More recent occurrences happen without Xid, when opening a new Firefox tab or switching tabs.
Only error observed:
kwin_wayland: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
After this message, the entire screen turns black.
No Xid, no GPU hang, no timeout messages are logged.
To Reproduce
Boot into Plasma 6 Wayland session
Use NVIDIA Open Kernel Module driver 590.48.01
Trigger GPU-accelerated workload:
Open Darktable and work with images
Or open Firefox and create / switch tabs
Bug Incidence
Sometimes
nvidia-bug-report.log.gz
More Info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached nvidia-bug-report.log.gz alongside the quoted Xid 69, EGL context, and GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT messages. Reproduce under Plasma 6 Wayland with driver 590.48.01 using Darktable or Firefox, then compare the resulting kernel and kwin_wayland logs; done means the black-screen failure is explained and a confirmed fix or reliable mitigation is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100