Post #3236915

2026-05-25 19:19 UTC

@shom@gts.shom.dev @fedops@fosstodon.org 22.04 still respected shutdown -r now, as did 24.04. This change didn't hit Ubuntu until 26.04. root@elden:/# reboot Operation inhibited by "jimbo" (PID 5571 "gnome-session-s", user jimbo), reason is "user session inhibited". User jimbo is logged in on tty2. Please retry operation after closing inhibitors and logging out other users. 'systemd-inhibit' can be used to list active inhibitors. Alternatively, ignore inhibitors and users with 'systemctl reboot -i'.

Replies (4)

@fedops@fosstodon.org 2026-05-25 19:32

@jimsalter@fosstodon.org @shom@gts.shom.dev aha. What systemd version is that?

Open ##3236916
@sequundi@social.tchncs.de 2026-05-25 20:56

@jimsalter@fosstodon.org @shom@gts.shom.dev @fedops@fosstodon.org right here it says: use -i. No need to rtfm 🤪🤪🤪🤪🤪 *runs away as fast as possible*

Open ##3236917
@jannem@fosstodon.org 2026-05-25 22:36

@jimsalter@fosstodon.org @shom@gts.shom.dev @fedops@fosstodon.org So I just did: $ systemctl reboot --when=+2min On my Ubuntu 26.04 with plenty of things running and it scheduled it and rebooted as expected. So whatever is going wrong doesn't always happen, at least. Edit: through ssh it fails, because there is a different user session (my desktop) active.

Open ##3236918
@becomethewaifu@tech.lgbt 2026-05-25 22:45

@jimsalter@fosstodon.org That says gnome asked it to inhibit logout due to a user application asking, usually gedit's "unsaved changes" in my experience? Not that it shouldn't ignore inhibitors by default when doing an interactive invocation of shutdown, but gnome-session-inhibit can show what's actually blocking the logout. (IMO an interactive invocation should just do an "are you sure? y/n" prompt at most)

Open ##3236933