On 12/05/2021 11.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.
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.
As there is little time for analysis, you (robin) could pipe the output from "top" to a terminal, and have the command ready in advance. top -d 5 -n 40 > top.log But it will show the most busy jobs, maybe not someone that is iddle just waiting. Maybe add "-b". Try first, with "-d 1 -n 2" for faster termination. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)