Comment # 3 on bug 1229813 from Simon Lees

(In reply to Thorsten Kukuk from comment #0)
> Services which require dbus have a dependency on dbus.socket in their
> service file.
> dbus-broker has no dbus.service file, thus this dependencies are broken and
> a boot only succeeds by pure luck.

This should work via dbus-broker.service having an alias to dbus.service

simon@tek-top ~ ➤  cat /usr/lib/systemd/system/dbus-broker.service
[Unit]
Description=D-Bus System Message Bus
Documentation=man:dbus-broker-launch(1)
DefaultDependencies=false
After=dbus.socket
Before=basic.target shutdown.target
Requires=dbus.socket
Conflicts=shutdown.target

[Service]
Type=notify
Sockets=dbus.socket
OOMScoreAdjust=-900
LimitNOFILE=16384
ProtectSystem=full
PrivateTmp=true
PrivateDevices=true
ExecStart=/usr/bin/dbus-broker-launch --scope system --audit
ExecReload=/usr/bin/busctl call org.freedesktop.DBus /org/freedesktop/DBus
org.freedesktop.DBus ReloadConfig

[Install]
Alias=dbus.service




(In reply to Thorsten Kukuk from comment #2)
> All boot issues this morning we put into the "soft-reboot" or "selinux"
> category were dbus problems as it looks like now.
> 
> Can we please drop dbus-1-daemon package and let dbus-broker install the
> service script as "dbus.service", so that all dependencies on dbus.socket
> work again?

dbus-1-daemon is still required in certain usecases (mostly gdm and test
suites) for dbus-run-session as dbus-broker does not have in built session
management.

All Fedora, Debian and upstream are shipping only a dbus-broker.service with an
alias to dbus.service so I would really prefer not to deviate unless someone
can come up with an exceptionally good reason.

We did notice https://bugzilla.suse.com/show_bug.cgi?id=1229745 with wicked
which is more of an issue of wicked not declaring it needs to start after dbus
because it uses it. I am submitting a fix for that now.