[kactivitymanagerd] [Bug 361702] Kactivitymanagerd doesn't close on shutdown and triggers 90 sec shutdown delay in systemd
https://bugs.kde.org/show_bug.cgi?id=361702 Ivan Čukićchanged: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 361702] Kactivitymanagerd doesn't close on shutdown and triggers 90 sec shutdown delay in systemd
https://bugs.kde.org/show_bug.cgi?id=361702 --- Comment #5 from Ivan Čukić--- This should be fixed by latest systemd + latest kamd - I'm not going to close it until it is confirmed. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 361702] Kactivitymanagerd doesn't close on shutdown and triggers 90 sec shutdown delay in systemd
https://bugs.kde.org/show_bug.cgi?id=361702 Ivan Čukićchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Ivan Čukić --- It seems this happens since my attempt to subvert the QtSQL bug. Hmh, I'll have to think of something else then. Thanks all :) -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 361702] Kactivitymanagerd doesn't close on shutdown and triggers 90 sec shutdown delay in systemd
https://bugs.kde.org/show_bug.cgi?id=361702 Argyris Mchanged: What|Removed |Added CC||argy...@gmail.com --- Comment #2 from Argyris M --- Created attachment 98746 --> https://bugs.kde.org/attachment.cgi?id=98746=edit systemd shutdown log I can confirm this on 5.6.3 too, on three different machines. It's been happening since 5.6.0. I am attaching the relevant part of the systemd shutdown log. The delay is short only because I have manually reduced the timeout. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 361702] Kactivitymanagerd doesn't close on shutdown and triggers 90 sec shutdown delay in systemd
https://bugs.kde.org/show_bug.cgi?id=361702 Ulysses Ribeirochanged: What|Removed |Added CC||ulysse...@gmail.com --- Comment #1 from Ulysses Ribeiro --- Same here. Running pgrep -a -u username on the debug shell gives: 699 /usr/bin/kactivitymanagerd start-daemon Then doing a pkill -u username, makes the shutdown continue immediately. It seems kactivitymanagerd is not responding to SIGTERM. Package version: 5.6.3 "kactivitymanagerd status" output: The service is running, version: 7.0.0 Cleaning up... -- You are receiving this mail because: You are watching all bug changes.