Tried with multiple clean installs and some testing, logging out stops working at an indeterminate point during setting up my system. The failure occurred after different steps in separate runs - once after setting up Flatpak, another after installing AMD drivers - suggesting that something in the setup process is breaking logout functionality. OS: Arch Linux
What I did:
- Perform a clean install.
- Log out to confirm functionality.
- Run setup scripts step by step, logging out and back in after each.
- At some point, logout fails.
I suspect possibly a misconfigured or conflicting systemd service(s).
What’s the best way to debug what’s preventing logout? Any relevant logs or system services I should inspect?
Hi - while this might be something being driven by something lower-level than Plasma itself, a good diagnostic starting point could be to look in your system logs using the journalctl command.
For example, if a logout attempt failed at 4:30 PM today, you could use sudo journalctl --since="2025-03-24 16:29:00" --until="2025-03-24 16:31:00" to look at the surrounding couple of minutes and see if any major crashes, errors or warnings are being reported there.
Feel free to post those in this topic, using the “Preformatted text” option in the formatting toolbar, and folks can help with possible troubleshooting ideas or places to check 
Thanks for the tip!
I think it suggests a bug? Or it’s unrelated?
Mar 25 15:37:47 zephyrus konsole[3980]: QThreadStorage: Thread 0x59fd9f1133b0 exited after QThreadStorage 9 destroyed
Mar 25 15:37:49 zephyrus kate[3587]: QThreadStorage: Thread 0x5f12280de2b0 exited after QThreadStorage 9 destroyed
Mar 25 15:37:49 zephyrus systemd[2046]: app-org.kde.kate@45bc2895da6145eba4520e5a188c922b.service: Consumed 1.285s CPU time, 57.3M memory peak.
Mar 25 15:37:50 zephyrus dolphin[3484]: QThreadStorage: Thread 0x570e94aa9ee0 exited after QThreadStorage 9 destroyed
Mar 25 15:37:50 zephyrus systemd[2046]: app-org.kde.dolphin@8fbad8469d8b41e6ad6b68a60d378709.service: Consumed 2.275s CPU time, 63M memory peak.
Mar 25 15:37:53 zephyrus systemd[2046]: app-firefox@a3496fd68b6e4779ab9066ffd83de344.service: Consumed 49.044s CPU time, 8.9G memory peak.
Mar 25 15:37:54 zephyrus plasmashell[2318]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce.
Mar 25 15:38:00 zephyrus systemd[2046]: Created slice Slice /app/dbus-:1.4-org.kde.LogoutPrompt.
Mar 25 15:38:00 zephyrus systemd[2046]: Started dbus-:1.4-org.kde.LogoutPrompt@0.service.
Mar 25 15:38:00 zephyrus ksmserver-logout-greeter[4077]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Mar 25 15:38:00 zephyrus plasmashell[2318]: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce.
Mar 25 15:38:00 zephyrus plasmashell[2318]: kf.windowsystem.wayland: Failed to recreate shadow for PlasmaQuick::AppletPopup_QML_179(0x567502302490, name="popupWindow")
Mar 25 15:38:00 zephyrus plasmashell[2318]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
Mar 25 15:38:02 zephyrus ksmserver-logout-greeter[4077]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Mar 25 15:38:02 zephyrus systemd[2046]: Created slice Slice /app/dbus-:1.4-org.kde.Shutdown.
Mar 25 15:38:02 zephyrus systemd[2046]: Started dbus-:1.4-org.kde.Shutdown@0.service.
Mar 25 15:38:02 zephyrus systemd[2046]: Stopped target plasma-workspace-wayland.target.
Mar 25 15:38:02 zephyrus systemd[2046]: Stopped target KDE Plasma Workspace.
Mar 25 15:38:02 zephyrus systemd[2046]: Stopped target KDE Plasma Workspace Core.
Mar 25 15:38:02 zephyrus systemd[2046]: Stopped target Startup of XDG autostart applications.
Mar 25 15:38:02 zephyrus systemd[2046]: Stopped target Session services which should run early before the graphical session is brought up.
Mar 25 15:38:06 zephyrus systemd[2046]: Started Konsole - Terminal.
Mar 25 15:38:06 zephyrus systemd[2046]: Started app-org.kde.konsole-4124.scope.
Mar 25 15:38:07 zephyrus warp-svc[1728]: 2025-03-25T08:38:07.167Z DEBUG actor_connectivity::connectivity: Routes changed:
Mar 25 15:38:07 zephyrus warp-svc[1728]: NewNeighbour; Destination: 192.168.110.1;
Mar 25 15:38:09 zephyrus sudo[4160]: arvigeus : TTY=pts/1 ; PWD=/home/arvigeus ; USER=root ; COMMAND=/usr/bin/journalctl '--since=2025-03-25 15:35:00' '--until=2025-03-25 15:40:00'
Mar 25 15:38:09 zephyrus sudo[4160]: pam_unix(sudo:session): session opened for user root(uid=0) by arvigeus(uid=1000)
It turned out to be Claudflare Warp’s fault.
1 Like