I compared the behavior with oracular, where the inhibit exists as well:
on oracular
-----------
* ubuntu@ubuntu:~$ reboot -> fails (inhibited)
* ubuntu@ubuntu:~$ sudo reboot -> succeeds
on plucky
---------
* ubuntu@ubuntu:~$ reboot -> fails (inhibited)
* ubuntu@ubuntu:~$ sudo reboot -> fails (inhibited)
Indeed, the behavior has changed in systemd 257. quote from the release notes
[1]:
* systemd-logind now always obeys block inhibitor locks, where
previously
it ignored locks taken by the caller or when the caller was root. A
privileged caller can always close the other sessions, remove the
inhibitor locks, or use --force or --check-inhibitors=no to ignore the
inhibitors. This change thus doesn't affect security, since everything
that was possible before at a given privilege level is still possible,
but it should make the inhibitor logic easier to use and understand,
and also help avoiding accidental reboots and shutdowns. New
'block-weak'
inhibitor modes were added, if taken they will make the inhibitor lock
work as in the previous versions. Inhibitor locks can also be taken by
remote users (subject to polkit policy).
[1] https://lwn.net/Articles/1001657/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092438
Title:
System fails to restart after install
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2092438/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
