What were you trying to do that didn't work?

Currently, dbus-broker uses inotify to reload when the configuration is detected or changed automatically. This may cause problems, the great example of that is https://issues.redhat.com/browse/RHEL-37686.

When installing systemd-resolved, which ships with dbus configuration, the existing mechanism fails because it expects the systemd-resolve user to exist, but it is created later in the transaction.

dbus-broker-launch[552]: Invalid user-name in /usr/share/dbus-1/system.d/org.freedesktop.resolve1.conf +16: user="systemd-resolve"

Steps to reproduce

# use CentOS Stream 10
dnf install systemd-resolved
systemctl start systemd-resolved
resolvectl status

This should work, but it hangs because it is trying to connect to dbus. systemctl reload dbus fixes this issue.

Potential Solution

Please implement the rpm file trigger for dbus configuration similarly to the systemd file trigger.

Useful links

• systemd file triggers Fedora Change - https://fedoraproject.org/wiki/Changes/systemd_file_triggers
• rpm documentation - https://rpm-software-management.github.io/rpm/manual/file_triggers.html
• systemd PR introducing rpm file triggers - https://github.com/systemd/systemd/pull/1909