Bug#931235: shutdown reboots immediately without dbus

[Antoine Beaupre]

Package: systemd-sysv
Version: 241-5
Severity: grave

I have somehow managed to install a buster system with systemd-sysv
(so it boots under systemd) and without dbus (probably because I
installed without recommends).

This has all sorts of ... er... interesting properties. The most
noticeable (and disturbing) one is that `shutdown -r +DELAY` doesn't
work anymore.

root at archive-01:~# shutdown -r +1 "test" 
Failed to connect to bus: No such file or directory
root at archive-01:~# 

At this point, my SSH connexion froze and the machine stopped
answering pings. I am not exactly sure what happens because I don't
have a console on the server, but I suspect it just did a hard reboot,
because normal shutdown procedures would have killed the sshd process
and therefore closed the connexion (instead of just hanging).

Therefore, not only the +1 minute delay is not respected, but the
shutdown procedure is bypassed completely. The server eventually *did*
reboot so it's not a full crash, but it's still pretty nasty.

I would recommend a hard Depends on dbus for the systemd-sysv package
(which provides the shutdown command) to resolve this problem.

And I think this should be fixed in buster, sorry for the last minute
bug report. :/ I really appreciate your work and systemd is generally
working very well for me, so thank you for that! :)

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd-sysv depends on:
ii  systemd  241-5

Versions of packages systemd-sysv recommends:
ii  libnss-systemd  241-5

systemd-sysv suggests no packages.

-- debconf-show failed

PS: this bug report was filed on a different machine than the original
one, but the environment should be similar (except the APT policy).