After automatic updating to:
KDE Plasma 6.6.5
KDE FW 6.26.0
QT version 6.11.1
Kernel version 7.09-ogc3.2.
Wayland
I only see a black screen afer the login screen.
Of course it could be any hardware confliciting, bu my pc runs a Nvidia RTX 3070, so the chance is big that that provides the issue.
Previous versions don’t give any issue.
My laptop has a Intel GPU also, and the update doesn’t bring any issues.
Does anyone else have issues now?
For the time being I disabled automatic updates, and rebooted in Ostree 1, hoping for a fix in the near future.
Thanks all.
I’m having the same exact issue, and I also have Intel/nvidia. After logging in, the screen is black, except the mouse pointer is visible and it works (even tho there’s nothing I can interact with, I can easily move it).
Yes indeed. And if you do cntr alt del, de shutdown screen appears, so realy seems like a graphical issue. But then I am not the only one, that give me hope
Looks like there’s an issue reported on the Bazzite github for that:
opened 11:17AM - 07 Jun 26 UTC
## Description
After updating from `bazzite-nvidia-open:43.20260420` → `bazzite… -nvidia-open:44.20260429` (F43→F44 transition), the GUI fails to load. Only a black screen with a cursor appears. Accessible only via Ctrl+Alt+F2 TTY.
`startplasma-wayland` from TTY works fine. The issue is specifically with `plasmalogin` not being able to access the DRM device.
## Hardware
- **CPU:** AMD Ryzen 9 9950X3D 16-Core (32 threads)
- **GPU:** NVIDIA RTX 4080 (AD103), Palit Microsystems
- **RAM:** 96 GB
- **Storage:** 3x NVMe (931 GB + 2x 1.9 TB)
- **Monitors:** DP-4 (3840x2160) + DP-5 (1920x1080)
## Software
- **Variant:** `bazzite-nvidia-open`
- **Working version:** `43.20260420` (Fedora 43, kernel 6.17.7, Nvidia 595.58.03)
- **Broken versions tested:** `44.20260429`, `44.20260515`, `44.20260605` (Fedora 44, kernel 7.0.9, Nvidia 610.43.02)
- Also tested `bazzite-nvidia` (closed driver, 580.159.04) — same bug
## bisect Results
| Version | Fedora | Result |
|---------|--------|--------|
| `43.20260420` | F43 | ✅ Works |
| `44.20260429` | F44 | ❌ Black screen |
| `44.20260515` | F44 | ❌ Black screen |
| `44.20260605` | F44 | ❌ Black screen |
Bug was introduced in the **F43→F44 transition** (between Apr 20 and Apr 29).
## Journal Errors (on broken versions)
```
kwin_wayland[...]: Failed to open drm device
kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Failed to get dynamic displays during device registration
kernel: nvidia 0000:01:00.0: [drm] Cannot find any crtc or sizes
```
## DRM Device Analysis
```
$ ls -la /dev/dri/
crw-rw----+ 1 root video 226, 1 card1
crw-rw-rw-. 1 root render 226, 128 renderD128
$ getfacl /dev/dri/card1
user::rw-
user:ginseng:rw- # ← only user has ACL
group::rw-
other::---
$ id plasmalogin
uid=967(plasmalogin) gid=967(plasmalogin) groups=967(plasmalogin)
# ↑ NOT in video group, NO ACL entry → cannot access /dev/dri/card1
```
- simpledrm grabs minor 0 (`card0`), nvidia-drm gets minor 1 (`card1`)
- `plasmalogin` session shows `Active=no` in loginctl → logind doesn't grant uaccess ACL
- Connectors ARE detected and show correct modes (DP-4 connected 4K, DP-5 connected 1080p)
## Workarounds Tried
| Workaround | Result |
|------------|--------|
| `startplasma-wayland` from TTY | ✅ Works (ginseng has ACL) |
| `nvidia-drm.modeset=1` kernel arg | ❌ No change |
| `initcall_blacklist=simpledrm_init` kernel arg | ❌ simpledrm still loaded |
| `usermod -aG video plasmalogin` | ❌ Doesn't persist on immutable OS |
| Rebase to `bazzite-nvidia` (closed driver) | ❌ Same bug |
| Rebase to older F44 versions | ❌ All broken |
| Rebase to `43.20260420` (F43) | ✅ Works |
## Related Issues
- #4763 — Black Screen when booting after update to Bazzite 44
- #4983 — Plasma Login black screen, greeter KWin fails to start
- #4822 — Desktop Environment not launching after update
- #4770 — After update to 44.20260429, only one monitor works
- #5045 — Regression from 595 (bazzite-nvidia-open 44.20260605)
There’s also a workaround in the 2nd post, but I don’t want to put it here since I’m not sure it’s the same problem/configuration. But, take a look.