Fedora Account System
Red Hat Associate
Red Hat Customer
I've noticed KDE desktop_login tests failing a few times in openQA lately. Each time, it seems like when we click "Log Out" and then "Log Out Now" on the overlay that pops up, the log out doesn't actually happen until 30 seconds later. Recent examples of this: https://openqa.fedoraproject.org/tests/4335201 https://openqa.fedoraproject.org/tests/4336905 https://openqa.fedoraproject.org/tests/4337858 The logs don't show anything in particular happening during those 30 seconds: Feb 24 09:14:36 fedora systemd[1329]: Started dbus-:1.1-org.kde.LogoutPrompt. Feb 24 09:14:36 fedora ksmserver-logout-greeter[2775]: libEGL warning: egl: failed to create dri2 screen Feb 24 09:14:36 fedora ksmserver-logout-greeter[2775]: libEGL warning: egl: failed to create dri2 screen Feb 24 09:14:36 fedora kernel: lockdown_is_locked_down: 5 callbacks suppressed Feb 24 09:14:36 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 09:14:36 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 09:14:36 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 09:14:36 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 09:14:36 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 09:14:36 fedora ksmserver-logout-greeter[2775]: static bool KX11Extras::compositingActive() may only be used on X11 Feb 24 09:14:37 fedora systemd[1329]: Started dbus-:1.1-org.kde.Shutdown. Feb 24 09:14:37 fedora systemd[1329]: dbus-:1.1-org.kde.LogoutPrompt: Consumed 602ms CPU time over 1.390s wall clock time, 109.1M memory peak. Feb 24 09:15:02 fedora systemd[1]: bluetooth.service - Bluetooth service skipped, unmet condition check ConditionPathIsDirectory=/sys/class/bluetooth Feb 24 09:15:02 fedora kdeconnectd[2049]: Cannot find Bluez 5 adapter for device search false Feb 24 09:15:07 fedora ksmserver[1720]: Failed to play sound with canberra: IO error Feb 24 09:15:07 fedora xwaylandvideobridge[2055]: QObject::disconnect: Unexpected nullptr parameter Feb 24 09:15:07 fedora systemd[1329]: Starting grub-boot-success.service - Mark boot as successful... Feb 24 09:15:07 fedora systemd[1329]: Stopped target plasma-workspace-wayland.target. That's from 4337858. The test execution log shows we clicked the Log Out Now button at 2026-02-24T14:14:39.135904Z (host system clock). It looks kinda like that click was just ignored, and instead the log out proceeded on the 30 second timer from the initial Log Out button click at XX:14:37 (hence it happened at XX:15:07). Not sure what component is responsible for this, please move as appropriate.
Aha, bit more info. So, this seems to have generalized out lately to something more like "sometimes clicking log out, reboot etc. entries does nothing". Here's another recent case: https://openqa.fedoraproject.org/tests/4431586#step/desktop_login/61 We match the "Restart" button there and click it, and then...nothing happens at all. No dialog pops up. The system never reboots. In the journal I see some juicier messages this time: Mar 13 07:19:02 fedora systemd[3286]: Started dbus-:1.2-org.kde.LogoutPrompt. Mar 13 07:19:03 fedora ksmserver-logout-greeter[4933]: libEGL warning: egl: failed to create dri2 screen Mar 13 07:19:03 fedora ksmserver-logout-greeter[4933]: libEGL warning: egl: failed to create dri2 screen Mar 13 07:19:03 fedora systemd[3286]: Starting grub-boot-success.service - Mark boot as successful... Mar 13 07:19:03 fedora systemd[3286]: Finished grub-boot-success.service - Mark boot as successful. Mar 13 07:19:04 fedora ksmserver-logout-greeter[4933]: static bool KX11Extras::compositingActive() may only be used on X11 Mar 13 07:19:04 fedora ksmserver-logout-greeter[4933]: Failed to get focus after 1 second, quitting Mar 13 07:19:04 fedora systemd[3286]: dbus-:1.2-org.kde.LogoutPrompt: Consumed 1.529s CPU time over 2.493s wall clock time, 207.2M memory peak. Can anyone look at this? It's quite a bad bug.
https://openqa.fedoraproject.org/tests/4429350#step/desktop_login/49 is another case where clicking "Log Out" did nothing (the confirmation popup didn't appear, the log out never happened). Similar messages: Mar 13 04:55:31 fedora systemd[1348]: Started dbus-:1.2-org.kde.LogoutPrompt. Mar 13 04:55:32 fedora ksmserver-logout-greeter[3014]: libEGL warning: egl: failed to create dri2 screen Mar 13 04:55:32 fedora ksmserver-logout-greeter[3014]: libEGL warning: egl: failed to create dri2 screen Mar 13 04:55:33 fedora ksmserver-logout-greeter[3014]: static bool KX11Extras::compositingActive() may only be used on X11 Mar 13 04:55:33 fedora ksmserver-logout-greeter[3014]: Failed to get focus after 1 second, quitting Mar 13 04:55:34 fedora systemd[1348]: dbus-:1.2-org.kde.LogoutPrompt: Unit process 3014 (ksmserver-logou) remains running after unit stopped. Mar 13 04:55:34 fedora systemd[1348]: dbus-:1.2-org.kde.LogoutPrompt: Consumed 1.986s CPU time over 3.197s wall clock time, 207.5M memory peak.
Interestingly I can't find any recent cases of the *initial* failure mode. Now all the failures seem to be this "Clicking the first button does nothing" case (with similar logs with the "Failed to get focus after 1 second, quitting" message), not the earlier "Clicking the confirm button on the popup doesn't work" case (with less expressive logs).
Interestingly, this also seems to be happening on F43. The earliest case I can see is https://openqa.fedoraproject.org/tests/4307629 from Feb 18.
Given that https://bodhi.fedoraproject.org/updates/FEDORA-2026-7ab9b19856 went stable Feb 17, that looks a lot like Plasma 6.6 introduced this.
So I suspect the cause of at least the *current* issues is https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/6200 . I ran a test. I did a scratch build with that timeout bumped from 1 second to 2 seconds: https://koji.fedoraproject.org/koji/taskinfo?taskID=143329440 . I set up a 'test cannon' in openQA - where we run the same test multiple times simultaneously - using a simplified test which just boots KDE, logs in, then immediately tries to log out. With the official package (1 second timeout), it failed 13 out of 19 times. With the scratch build (2 second timeout), it failed 1 out of 19 times. That seems pretty good! We might arguably want to go to a 3 second timeout, but 2 is clearly a big improvement. I'll send a PR upstream.
FEDORA-2026-1b70e90f40 (plasma-workspace-6.6.2-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-1b70e90f40
FEDORA-2026-542e86d454 (plasma-workspace-6.6.2-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-542e86d454
FEDORA-2026-6c6c879616 (plasma-workspace-6.6.2-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-6c6c879616
FEDORA-2026-1b70e90f40 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-1b70e90f40` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-1b70e90f40 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-542e86d454 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-542e86d454` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-542e86d454 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-6c6c879616 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-6c6c879616` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6c6c879616 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-542e86d454 (plasma-workspace-6.6.2-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-6c6c879616 (plasma-workspace-6.6.2-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-a901be219b has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-a901be219b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-a901be219b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-a901be219b (aurorae-6.6.3-1.fc42, bluedevil-6.6.3-1.fc42, and 72 more) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.