Control: severity -1 normal Hi!
Thanks for your quick reply! I tried to make this bug reproducible and
eventually succeeded: The crucial point was, that the package
installation must happen *before* systemd considers the system fully
booted, i.e. by installing the package inside "/etc/rc.local". This
means:
1. This is certainly a corner case, so I have downgraded the severity
to "normal".
2. Depending on what our expectations on systemd are, this might be no
bug at all.
3. If it is a bug, it is probably not in the dbus package, but rather
in the init-system-helpers or systemd package.
If you (or the systemd maintainers) are interested, you can reproduce
this bug with the attached script: Just run it as root and you should
eventually get a login prompt. Login as root (no password required) and
run "systemctl status dbus". The output should look like this:
root@shepard:~# systemctl status dbus
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor
preset: enabled)
Active: failed (Result: exit-code) since Sun 2017-02-12 00:17:56
CET; 3min 29s ago
Docs: man:dbus-daemon(1)
Main PID: 192 (code=exited, status=1/FAILURE)
Feb 12 00:17:56 shepard systemd[1]: Started D-Bus System Message Bus.
Feb 12 00:17:56 shepard dbus-daemon[192]: Failed to start message bus:
No socket received.
Feb 12 00:17:56 shepard systemd[1]: dbus.service: Main process exited,
code=exited, status=1/FAILURE
Feb 12 00:17:56 shepard systemd[1]: dbus.service: Unit entered failed
state.
Feb 12 00:17:56 shepard systemd[1]: dbus.service: Failed with result
'exit-code'.
root@shepard:~#
However, please also feel free to simply close this as NOTABUG. Thanks
again for your quick reply!
Best regards
Alexander Kurtz
reproduce-854911.sh
Description: application/shellscript
signature.asc
Description: This is a digitally signed message part
