** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
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 notification
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/209
** Changed in: systemd
Status: Unknown => New
--
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:
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 re
https://github.com/systemd/systemd/issues/36786
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/systemd/systemd/issues #36786
https://github.com/systemd/systemd/issues/36786
** Also affects: systemd via
https://github.com/systemd
I have made an attempt using `systemctl reboot --check-inhibitors=no`
but it fails with
"Call to reboot failed: Interactive authentication required."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092
In the live session, calling `systemctl reboot` (or /sbin/reboot) as
root produces the following error:
# systemctl reboot
Operation inhibited by "ubuntu" (PID 2297 "gnome-session-b", user ubuntu,
reason is "user session inhibited".
User ubuntu is logged in on tty2.
Please retry operation after c
Thank you for the report!
Reproduced the issue today with extra logging enabled.
"Call to Reboot failed: Access denied"
2025-03-19 10:04:23,950 DEBUG root:38 start: subiquity/Shutdown/shutdown:
mode=REBOOT
2025-03-19 10:04:23,950 DEBUG subiquitycore.utils:179 astart_command called:
['systemd-r
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: subiquity (Ubuntu)
Milestone: None => ubuntu-25.04
** Changed in: subiquity (Ubuntu)
Assignee: (unassigned) => Olivier Gayot (ogayot)
--
You received this bug notification because you are a m
