Skip to content

kms-modifiers for Xwayland acceleration is not enabled by default on Gnome+Nvidia images yet #3117

Description

@msmafra

Describe the bug

Hello there!
IA bit more than a year back, I opened this issue: #1567 pointing out that kms-modifiers must be enabled, as it is a requirement stated in Chapter 40 or 38, depending on the version of the NVIDIA driver documentation, since 470.42.01 and still in 580.76.05 and related to 3D accelerated rendering for OpenGL, Vulkan and VDPAU on Xwayland.

What did you expect to happen?

Expected kms-modifiers to be enabled by default for Gnome images on NVIDIA drivers.

Output of bootc status

❯ sudo bootc status
● Booted image: ghcr.io/ublue-os/bluefin-nvidia-open:stable
        Digest: sha256:1f3211e557412ed5421a8abf3c7ef75d60849e7e9c3c11bc315c476ea40dd967 (amd64)
       Version: 42.20250831.1 (2025-08-31T06:29:43Z)

  Rollback image: ghcr.io/ublue-os/bluefin-nvidia-open:stable
          Digest: sha256:ca4e7f77d7eb9e4312818013261f190361b4be380e5a5437cfd2fdcd25661ffb (amd64)
         Version: 42.20250824.1 (2025-08-24T06:25:28Z)

Output of groups

❯ groups
zum wheel

Extra information or context

I imagine, guessing here, that maybe some problems that are usually reported when using Gnome mostly related to games, have to do with this. Obviously I do not have the knowledge on how to benchmark this nor have another computer to do tests on it.

I also wonder why this is still an experimental feature on Gnome, since the driver 470.42.01 is from 2021-06-22 and probably this feature is older than that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/nvidiaIssues specific to NVIDIA GPU support, drivers, and compatibilitykind/enhancementNew feature, don't implement without a spec and consensus

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions