[Pkg-utopia-maintainers] Bug#986541: avahi-daemon: fail to upgrade from 0.7-4+b1 to 0.7-4+deb10u1

[Simon McVittie]

On Wed, 07 Apr 2021 at 18:58:34 +0200, Michael Biebl wrote:
> Simon,
> 
> does that ring a bell?
> 
> > avril 07 11:05:26 zarbi dbus-daemon[598]: [system] Reloaded configuration
> > avril 07 11:05:26 zarbi dbus-daemon[598]: [system] Activating systemd to hand-off: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.1859' (uid=0 pid=10476 comm="/usr/sbin/cups-browsed ")
> > avril 07 11:05:26 zarbi dbus-daemon[598]: [system] Activating systemd to hand-off: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.1858' (uid=0 pid=16027 comm="/usr/bin/gdbus call --system --dest org.freedeskto")
> > avril 07 11:05:51 zarbi dbus-daemon[598]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
> > avril 07 11:05:51 zarbi dbus-daemon[598]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out (service_start_timeout=25000ms)
> > avril 07 11:05:51 zarbi dbus-daemon[598]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out (service_start_timeout=25000ms)

Looks like systemd (pid 1) never managed to connect to dbus-daemon --system?

What's meant to happen is that systemd (pid 1) automatically connects to
the system bus and requests its well-known name org.freedesktop.systemd1.
When dbus-daemon --system sees that this has happened, it asks systemd
to start any services that have a SystemdService field.

In this case it looks like systemd either never connected to the system
bus, or never successfully requested its well-known name
org.freedesktop.systemd1.

Were there any warnings related to this earlier in the log?

Do the commands 'realpath /var/run/dbus/system_bus_socket' and
'realpath /run/dbus/system_bus_socket' both print the same thing on the
affected system?

    smcv