Universal BlueUB
Universal Blue•6d ago
Jenterrobahne

sddm fails to start on v43

System Information:
 
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
                   Digest: sha256:cce2eaa398efc42e0ff3c14c0d54a024a987cde0feeb3b72d7970d0bf54883b8
                  Version: 43.20251210.1 (2025-12-10T21:44:16Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
                   Digest: sha256:924cc92015b45166531d247f540be8f36b9cd461cb68bcaaedfa78da09c25e95
                  Version: 42.20251018 (2025-10-18T21:38:37Z)
                   Pinned: yes

Logs This Boot: https://paste.centos.org/view/44bf2aab

Logs Last Boot: https://paste.centos.org/view/6a69858d

Hardware: https://paste.centos.org/view/3ffd73e1

Running a GTX 750 Ti on a desktop.

On v42 everything works well. I have been holding off upgrading because of this bug but after this week's release, tried rebasing again and figured it was time to post.

Symptoms: boot happens and then when sddm starts I get a corrupted screen (white snow). I can switch to tty2, log in, and run startplasma-wayland and it works fine. It's just sddm it seems.

In the logs I see Dec 11 17:49:07 bazzite sddm-helper-start-wayland[1397]: "Accepting client connections on sockets: QList(\"wayland-0\")\nkwin_core: Failed to open drm node: \"/dev/dri/card0\"\nkwin_wayland_drm: No suitable DRM devices have been found\n" as my best guess of what looks suspicious.
Was this page helpful?