https://bugs.kde.org/show_bug.cgi?id=434403
--- Comment #1 from Matt Fagnani <matthew.fagn...@utoronto.ca> --- I've continued to see this problem when I've logged out of Plasma 5.21.4 with KF 5.80.0 and logged in within about 40 seconds. If I logged in again after about 40-60 seconds, then Plasma started normally. When I rebooted or shut down from Plasma, a systemd message like "A stop job is running for User Manager for UID 1000" was shown for 40-60 seconds before the reboot or shutdown happened most of the time. I noticed in the KF 5.81.0 changelog for kded https://kde.org/announcements/frameworks/5/5.81.0/ the commit "make kded shut down cleanly during systemd session teardown" https://invent.kde.org/frameworks/kded/-/commit/96aa058b2b70bc19484e649b5bfcbb86d36336ff I changed /usr/lib/systemd/user/plasma-kded.service like in that commit by adding the line PartOf=graphical-session.target I logged in and out multiple times after that making that change, kded5 didn't abort during logout according to coredumpctl. Plasma started normally each time I logged in again within 10 seconds of logging out. That commit might be sufficient to avoid this problem. kwalletd5 still aborted when logging out, though kwalletd5 appears to just have a dbus-activated systemd service /usr/share/dbus-1/services/org.kde.kwalletd5.service and not a user session one like kded. -- You are receiving this mail because: You are watching all bug changes.
