KDE UI Shutdown broken, but not the command-line

Support KDE Plasma
1

What triggered

I installed updates that have come out over the past day/days.

Problem

When shutting the laptop down via the UI, the laptop goes to a black screen with the mouse cursor still visible and hangs there. This happens every single time shutdown in such way is attempted, here are the last logs since when shutdown is initiated.

Oct 02 21:48:08 my_username systemd[654]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
Oct 02 21:48:08 my_username systemd[654]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
Oct 02 21:48:08 my_username systemd[1]: Starting Network Manager Wait Online...
Oct 02 21:48:08 my_username systemd[1]: Starting PackageKit Daemon...
Oct 02 21:48:08 my_username PackageKit[1270]: daemon start
Oct 02 21:48:08 my_username systemd[1]: Finished Network Manager Wait Online.
Oct 02 21:48:08 my_username systemd[1]: Reached target Network is Online.
Oct 02 21:48:08 my_username systemd[1]: Started PackageKit Daemon.
Oct 02 21:48:10 my_username systemd[654]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown.
Oct 02 21:48:10 my_username systemd[654]: Started dbus-:1.2-org.kde.Shutdown@0.service.
Oct 02 21:48:10 my_username kded6[774]: Service  ":1.54" unregistered
Oct 02 21:48:10 my_username kded6[774]: Service  ":1.55" unregistered
Oct 02 21:48:10 my_username msm_kde_notifier[1047]: Shutting down MSM Notifier...
Oct 02 21:48:10 my_username systemd[654]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Oct 02 21:48:10 my_username systemd[654]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.
Oct 02 21:48:10 my_username systemd[654]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Consumed 511ms CPU time, 88M memory peak.
Oct 02 21:48:10 my_username systemd[654]: app-pamac\x2dtray\x2dplasma@autostart.service: Consumed 966ms CPU time, 75.7M memory peak.
Oct 02 21:48:10 my_username plasmashell[804]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:136: TypeError: Cannot r>
Oct 02 21:48:10 my_username plasmashell[804]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:250: TypeError: Cannot r>
Oct 02 21:48:10 my_username plasmashell[804]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Oct 02 21:48:10 my_username plasmashell[804]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo"
Oct 02 21:48:10 my_username plasmashell[804]: org.kde.pulseaudio: No object for name "alsa_input.pci-0000_00_1f.3.analog-stereo"
Oct 02 21:48:10 my_username plasmashell[804]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 02 21:48:10 my_username plasmashell[804]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 02 21:48:10 my_username plasmashell[804]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 02 21:48:10 my_username plasmashell[804]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 02 21:48:10 my_username plasmashell[804]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 02 21:48:10 my_username plasmashell[804]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 02 21:48:10 my_username plasmashell[804]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 02 21:48:10 my_username plasmashell[804]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 02 21:48:10 my_username plasmashell[804]: QObject::startTimer: Timers can only be used with threads started with QThread
Oct 02 21:48:10 my_username systemd[654]: plasma-plasmashell.service: Consumed 8.403s CPU time, 522.3M memory peak.
Oct 02 21:48:11 my_username ksmserver[772]: org.kde.kf6.ksmserver: Connection rejected: ksmserver is shutting down
Oct 02 21:48:34 my_username systemd-logind[521]: Power key pressed short.
Oct 02 21:48:34 my_username systemd[654]: Started dbus-:1.2-org.kde.LogoutPrompt@1.service.
Oct 02 21:48:36 my_username systemd-logind[521]: Power key pressed short.
Oct 02 21:48:36 my_username systemd[654]: Started dbus-:1.2-org.kde.LogoutPrompt@2.service.

Bypass

I’ve tried opening up a terminal, and typing in: shutdown now.

This way of shutting down works no problem. So it’s a KDE issue, and nothing shutdown or unkillable process related.

Hope this helps the devs to fix whatever the broken package is.

1 Like
2

System Settings → System → Session

Set it to start with an empty session, save the changes and reboot. After the reboot you can try re-enabling saved sessions, although there is no guarantee that it will continue working.

It’s a known bug.

3 Likes
3

Setting “Session Restore” to “Start with an empty session” solves the problem.

However, setting it back to “When session was manually saved” brings the problem back even after a reboot.

Hopefully this session restore is not sleep or hibernation related?
(it would suck to lose work progress due to it trying to start with an empty session after hibernation)

2 Likes
4

No, it’s about restoring the previous session on login. Resuming from hibernation should already do that by itself, but in another way.

Session restore keeps track of what apps you had open, while resuming from hibernation simply copies the saved RAM contents from the swap device back into RAM.

2 Likes
5

Thanks, that clears it up.

1 Like
6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.