Bug 2490995

Summary: Plasma session fails to start on Wayland with Qt apps failing to initialize display on Nouveau
Product: [Fedora] Fedora Reporter: go_noisemaker
Component: qt6-qtbaseAssignee: Jan Grulich <jgrulich>
Status: NEW --- QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 44CC: go_noisemaker, jgrulich, kde-sig
Target Milestone: ---Keywords: Desktop, Regression, Upgrades
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journalctl logs of failed plasma session startup none

Description go_noisemaker 2026-06-20 07:25:07 UTC
I just upgraded my system to Linux 7.0 and KDE Plasma 6.7 (https://bodhi.fedoraproject.org/updates/FEDORA-2026-279229780a) and now I'm presented with just a blinking cursor after the Plymouth boot screen.

I found that:
- plasma-login-manager fails to start
- SDDM similarly fails to start
- GDM works fine
- Plasma (Wayland) sessions, from GDM, similarly fail to start
- GNOME sessions, from GDM, work fine

Notable logs from kwin_wayland:
> Failed to open /dev/dri/card0 device (Device or resource busy)
> No suitable DRM devices have been found

Many other KDE components (kded6, powerdevil, kaccess, etc.) are all crashing instantly on startup with Qt platform initialization errors:
> the application failed to start because no Qt platform could be initialized
> Could not load the Qt platform plugin "wayland" even though it was found
> Could not load the Qt platform plugin "xcb" even though it was found

Reinstalling mesa-dri-drivers, qt6-qtwayland and clearing the QML caches (to the best of my abilities) did not solve the problem.

Reverting to Linux 6.9 from the GRUB boot selector did not help either.

Starting Plasma in a X11 session, in contrast, works fine.

Similar case in the wild (reporter + 5 me-too's):
https://www.reddit.com/r/cachyos/comments/1ua1hze/update_broke_my_plasma/
> I updated and then went to sleep last night, I wake up this morning to find that whenever I login I always end up on a black screen with a cursor

Attaching logs of a failed attempt at starting a Plasma session.

Reproducible: Always

Steps to Reproduce:
1. Have plasma-login-manager or SDDM set as the desktop manager
2. Boot system

...or...

1. Have GDM set as the desktop manager
2. Log in with a Plasma session
Actual Results:
Blank screen with cursor blinking

Expected Results:
Login screen or desktop showing up normally

Additional Information:
GPU: Nvidia GeForce GTX 970
Driver: Nouveau
Kernel: 7.0.12-201.fc44.x86_64
Packages:
- qt6-qtbase: 6.11.1-1.fc44
- plasma-desktop: 6.7.0-1.fc44

Comment 1 go_noisemaker 2026-06-20 07:35:42 UTC
Created attachment 2145976 [details]
journalctl logs of failed plasma session startup

Comment 2 go_noisemaker 2026-06-20 10:00:45 UTC
Addendum: Plasma works when starting a X11 session, so it's just a problem with Wayland.

Comment 3 go_noisemaker 2026-06-20 10:03:17 UTC
Upstream KDE bug: https://bugs.kde.org/show_bug.cgi?id=521837

Comment 4 go_noisemaker 2026-06-28 15:24:19 UTC
Update: working again with Plasma 6.7.1 (or something else in the FEDORA-2026-5d22b951cf update fixed it).

Still, that was scary. I hope nothing like this happens again, especially given that Plasma 6.8 is going to drop Wayland.

Comment 5 go_noisemaker 2026-06-28 15:26:19 UTC
> drop Wayland

Of course I meant X11 there. Sorry for confusing.