On Thu, 2022-07-14 at 17:36 +0100, Patrick O'Callaghan wrote: > On Sun, 2022-05-01 at 12:14 +0100, Patrick O'Callaghan wrote: > > > This has been happening for IIRC) several months now at least: > > > > > > $ journalctl --boot=-1 --reverse > > > ... > > > May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Consumed > > > > > > > 18.380s CPU time. > > > May 01 10:44:26 Bree systemd[1210]: Stopped KDE Daemon. > > > May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Failed > > > with > result 'timeout'. > > > May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Main > > > process > exited, code=killed, status=9/KILL > > > May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Killing > > > > > > > process 1791 (ProfilesWatcher) with signal SIGKILL. > > > May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: Killing > > > > > > > process 1722 (kded5) with signal SIGKILL. > > > May 01 10:44:26 Bree systemd[1210]: plasma-kded.service: State > > > > 'stop-sigterm' timed out. Killing. <-----------------------* > > > May 01 10:43:03 Bree systemd[1]: Unmounted /run/user/0. > > > May 01 10:43:03 Bree systemd[1]: run-user-0.mount: Deactivated > > > > successfully. > > > May 01 10:43:03 Bree systemd[1]: Unmounted /run/user/990. > > > May 01 10:43:03 Bree systemd[1]: run-user-990.mount: Deactivated > > > > > > > successfully. > > > May 01 10:43:03 Bree systemd[1]: Stopped Network Manager Wait > > > Online. > > > ... > > > > > > > > > Any idea why? I see some apparently related BZ entries dating > > > back > > > a > > > couple of years, but nothing recently. > > I posted the above a couple of months back, but haven´t seen any > resolution so far. Google finds a few references to similar issues > but > they seem related to Wayland, while I'm using exclusively X11. > > The problem appears to be related to plasma-kded.service and happens > even when I explicitly log out before shutting down. > > I've reported it at: https://bugs.kde.org/show_bug.cgi?id=456713 See the above URL for details, but basically the Users list suggested a workaround to shorten the timeout. That still doesn't explain why kded is hanging. It's clearly waiting for *something* but there's no indication of exactly what. poc _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
