NVIDIA / NVIDIA/open-gpu-kernel-modules

KWin Wayland DRM atomic commit failure causing crash loop (open GPU kernel modules)

Open
#990 12 comments 7 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

580.119.02

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

NixOS 25.11 (Xantusia)

Kernel Release

Linux nixos 6.18.1-zen1

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

NVIDIA GeForce RTX 3060 Ti

Describe the bug

KWin fails to reliably apply DRM atomic modesetting when running a Plasma Wayland session on NVIDIA GPUs using the open GPU kernel modules.

During Wayland startup and output configuration, KWin reports DRM atomic modeset and commit failures with “Permission denied”. In some cases this results in a crash loop during login via SDDM; in other cases the session remains active but output configuration fails, indicating an intermittent DRM atomic failure in the NVIDIA driver.

The GPU is correctly assigned as DRM master, and the issue does not occur on AMD or Intel hardware with the same software stack.

To Reproduce

Preconditions:

  • NVIDIA GPU
  • NVIDIA proprietary userspace with open GPU kernel modules (nvidia-open)
  • DRM modesetting enabled
  • KDE Plasma 6.x, KWin 6.x, SDDM
  • Wayland session

Steps:

  • Boot the system normally
  • At SDDM, select “Plasma (Wayland)”
  • Log in
  • During startup or display configuration, KWin reports DRM atomic failures

Observed journal messages include:

  • “Atomic modeset test failed! Permission denied”
  • “atomic commit failed: Permission denied”
  • “Applying output configuration failed”
Bug Incidence

Sometimes

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

drm_NVIDIA.log
journal_kwin_wayland.log
kwin_wayland.log
nvidia-smi.txt
seat0.txt
uname.txt

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

Start with the attached drm_NVIDIA.log, journal_kwin_wayland.log, kwin_wayland.log, nvidia-bug-report.log.gz, and the reported kernel and driver versions. Reproduce the Plasma Wayland login and output-configuration sequence on the RTX 3060 Ti, then compare the DRM atomic failure messages with the observed crash loop. Done means the failure is explained and the session no longer crashes or loses output configuration under the stated setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux, nixos
Domain
computer-graphics, desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.