https://bugs.kde.org/show_bug.cgi?id=485011
--- Comment #10 from Malte S. Stretz <m...@apache.org> --- I found this: > systemd has a minimal transaction system: if a unit is requested to start up > or shut down it will add it and all its dependencies to a temporary > transaction. Then, it will verify if the transaction is consistent (i.e. > whether the ordering of all units is cycle-free). If it is not, systemd will > try to fix it up, and removes non-essential jobs from the transaction that > might remove the loop. Also, systemd tries to suppress non-essential jobs in > the transaction that would stop a running service. Finally it is checked > whether the jobs of the transaction contradict jobs that have already been > queued, and optionally the transaction is aborted then. If all worked out and > the transaction is consistent and minimized in its impact it is merged with > all already outstanding jobs and added to the run queue. Effectively this > means that before executing a requested operation, systemd will verify that > it makes sense, fixing it if possible, and only failing if it really cannot > work. Source: https://www.freedesktop.org/software/systemd/man/latest/systemd.html The root cause here seems to be that all units are transitioned to stopped except graphical-session which makes the whole session more or less a zombie. Maybe if the stopping of graphical-session could be marked as an essential job somehow the whole transaction would fail which should be a better outcome than this. -- You are receiving this mail because: You are watching all bug changes.
