Transcript:
Two panel meme.
Top panel: Woman in the front seat of a car screaming at a child in the rear seat. She’s saying “Why can’t you just shutdown?”
Bottom panel: A child screaming “A stop job is running for Session c2 of user … (1:30 / no limit)”
Why? You can bypass it immediately if it’s a one-off, or go update the unit configuration to have a short timeout if it’s a regular error.
More likely though, it’s something that should actually be fixed, like a misconfigured fstab. Systemd is rarely the problem here.
how do you bypass it? didn’t know its a thing
If you hit Ctrl-Alt-Delete 7 times in 2 seconds it will skip immediately
Unless the culprit is that one process permanently stuck in uninterruptible disk sleep, in which case the timer would just perpetually go up, and pressing 7x Ctrl-Alt-Del as you mentioned will simply shut down systemd and the kernel itself will start complaining (faulty hardware can cause this)