Comment 61 for bug 1871538

Quoting upstream systemd developers (https://github.com/systemd/systemd/issues/22737#issuecomment-1077682307):
"We essentially traded one problem (lockup when starting services) for another (the failure described in this commit).
I actually think that the lockup is worse. Here there is a simple solution: switch from dbus-daemon to dbus-broker. [...]

A proper fix will most likely be to make all dbus calls asynchronous in systemd, but that is a lot of work and it's unclear when/if it'll happen. The regression is unfortunate, but I don't think we can fix it in reasonable time."

So I wonder what's the best path forward in Ubuntu... if we revert, we'll re-introduce the lockup/timeout problem with dbus-daemon. If we keep the current version, fwupd-refresh.service is broken.

The comment at https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992 suggests that disabling the DynamicUser= setting makes the service work again. Maybe that's worth a try, in order to get both problems solved? (i.e. shipping an override config for fwupd)

$cat /etc/systemd/system/fwupd-refresh.service.d/override.conf
[Service]
DynamicUser=no