Black screen after login to kde since update

Ask Fedora
1

This has been an issue since I ran updates 2 days ago (12/02/25). When logging in to kde from gdm with the laptop connected to a dock, both dock connected screens remain blank, I have the laptop closed when connected to the dock.
This setup has worked fine for a couple of years, I can log in to gnome and everything works correctly.
When logging in to kde the login splash screen does not appear but the sounds do work and looking at the logs seems to show that the login succeeded and the desktop should be visible, although I am no expert at diagnosing issues from the logs!
Running Fedora 41 with all the latest updates on a Dell Precision 7760 connected to a Dell wd19dc usb-c dock with 2 monitors connected.

At the moment I’m just using gnome if I connect to the dock in the hope that whatever causes the issue gets fixed in the future.

2

I have a desktop system with KDE and 2 monitors. KDE has started to prefer one monitor, despite the other set as “primary”. With Gnome I often left the non-primary monitor turned off if I didn’t need the extra screen area. I removed “rhgb quiet” from the kernel command line, and both monitors display boot messages, so it is KDE that is confused.

Linux collects massive detail that can be viewed with journalctl. Here, a number of entries indicate a problem:

$ journalctl --no-hostname -b -g screen|cat
[... omit pre-boot entries ...]
Feb 14 10:28:02 dbus-broker-launch[3270]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Feb 14 10:28:04 systemd[3250]: Starting plasma-ksplash.service - Splash screen shown during boot...
Feb 14 10:28:05 kded6[3845]: xsettingsd: Created window 0xe00001 on screen 0 with timestamp 1052683
Feb 14 10:28:07 systemd[3250]: Starting app-orca\x2dautostart@autostart.service - Orca Screen Reader...
Feb 14 10:28:07 org_kde_powerdevil[3818]: org.kde.powerdevil: Handle button events action could not check for screen configuration
Feb 14 10:28:07 systemd[3250]: Condition check resulted in app-orca\x2dautostart@autostart.service - Orca Screen Reader being skipped.
Feb 14 10:28:07 systemd[3250]: Finished plasma-ksplash.service - Splash screen shown during boot.
Feb 14 11:19:25 dbus-broker-launch[9294]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Feb 14 11:19:41 dbus-broker-launch[9294]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Feb 14 11:19:41 dbus-broker-launch[3270]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Feb 14 11:19:41 dbus-broker-launch[9294]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Feb 14 11:19:41 dbus-broker-launch[3270]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Feb 14 11:20:20 dbus-broker-launch[9727]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Feb 14 11:28:14 dbus-broker-launch[11949]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.

I’m in Canada – currently too busy shovelling snow and hacking ice to investigate further.

3

A morning without added snow and ice, so I applied updates and the is not named after the D-Bus name errors are still present.

I found https://discuss.kde.org/t/frustrating-issues-with-kde-not-remembering-monitor-arrangement-and-panel-settings/28621 which provides a manual configuration example to work around the issues. It seem lack of (enforced?) standards for ways displays identify themselves to the system is making it hard to fix these issues.