![](https://seccdn.libravatar.org/avatar/34c7301d6b7738837a6fc69e1c0ef8bc.jpg?s=120&d=mm&r=g)
On 3/17/19 6:44 AM, Felix Miata wrote:
This huge reboot/shutdown delay is highly annoying. When shutdown needs to happen, it needs to happen now, not at the whim of systemd. I haven't figured out what triggers it, but it seems like maybe something that happens during zypper dup related to KDM(3 or 4) or Plasma5. It doesn't always happen. Last to happen here was on TW20190314 host big31 on first post-dup boot. What make ps -A produce " 983 ? 00:00:00 (sd-pam)"? What exactly is "User Manager"? Is this just happening to me?
Happens to me as well, on a casual home desktop (no NFS or other fanciness). When I have no patience I slowly start executing SysRq REISUB[1][2], and at some point (i.e. after E or after I) it gets through and shuts down/reboots. In general, RESIUB is the only way to 'safely kill' a system that needs a hard reboot. Some keyboards don't support n-key rollover, so to do it on them, you press Alt, press PrtSc (that can be two keys, so in total -- 3 keys pressed), release PrtSc, press R, wait 2-4 seconds, press I, ..., release Alt. Make sure you try it in a linux console on a properly working session first, where you can see if the system reacts somehow (and if you press the buttons correctly), because in a freezed system you will be doing it blindly. [1]: http://blog.kember.net/articles/reisub-the-gentle-linux-restart/ [2]: https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org