https://bugs.kde.org/show_bug.cgi?id=523101
--- Comment #16 from [email protected] --- Okay, I think I mostly understand what happened. After the crash, powerdevil closed its dbus connection. Then systemd saw that the dbus connection was closed and send the SIGTERM signal (see the docs for dbus systemd services under https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html?#Type=). The service stopped because of the signal. Since sigterm is considered a clean exit, the service is not restarted. The fix that I proposed indeed would fix it in this case. Quote from systemd docs: "Once the bus name is released the service is considered being no longer functional which has the effect that the service manager attempts to terminate any remaining processes belonging to the service. Services that drop their bus name as part of their shutdown logic thus should be prepared to receive a SIGTERM (or whichever signal is configured in KillSignal=) as result." -- You are receiving this mail because: You are watching all bug changes.
