On 12/05/2021 21:28, Andrei Borzenkov wrote:
On Wed, May 12, 2021 at 11:41 AM Robin Klitscher <robin.klitscher@gmail.com> wrote:
If this has been asked before, I’ve missed it and apologise. It’s certainly been asked elsewhere, though with no clear answer.
Because there is no universal clear answer.
Thank you for that. I'd thought as much.
Frequently, but not always, when closing (or rebooting) Leap 15.2, the shutdown stalls for 90 seconds with a message “A stop job is running for Session 2 of user <xxxx>”, together with a register counting down from 1 minute 30 seconds. When the countdown reaches zero the shutdown completes. There’s no other diagnostic information.
...
Assuming the problem does lie somehow with systemd-logind on shutdown, is there something else I can do to fix it?
Find out what process did not stop when the user session stops. Logout, login as a different user (preferably on console to make less noise) and check what processes from your user remain.
You're saying that the problem lies with something other than the process around systemd-logind that showed up in the log? No matter; the situation is obviously more complicated than it seems at first sight. In that it's an annoyance rather than a showstopper, and is partly resolved by reducing the default timeout from 90 sec to 10 sec, it's simpler just to live with it. Thanks again for your interest. -- Robin K Wellington "Harbour City" New Zealand