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

Automatic handling of user/group creation using sysusers during installation happens too late, causing dbus-broker reloading itself ignoring added access rules due to the user not existing.

Aug 07 11:55:35 localhost.localdomain dbus-broker-launch[1016]: Noticed file-system modification, trigger reload.
Aug 07 11:55:35 localhost.localdomain dbus-broker-launch[1016]: Looking up NSS user entry for 'gnome-remote-desktop'...
Aug 07 11:55:35 localhost.localdomain dbus-broker-launch[1016]: NSS returned no entry for 'gnome-remote-desktop'
Aug 07 11:55:35 localhost.localdomain dbus-broker-launch[1016]: Invalid user name 'gnome-remote-desktop' in service file '/usr/share/dbus-1/system-service>

The issue is that dbus-broker notices files changes and reloads, but user creation happens long after that, after %post.

What is the impact of this issue to you?

Installing gnome-remote-desktop requires one to manually call `systemctl reload dbus.service` or rebooting, before being able to use the package.

Please provide the package NVR for which the bug is seen:

systemd-257-11.el10.x86_64

How reproducible is this bug?:

Install gnome-remote-desktop and look at the dbus.service logs.

Expected results

User creation using sysusers being compatible with dbus-broker.

Actual results

User creation using sysusers doesn't work with dbus-broker access rules.

Notes

Arguably, this could be considered a dbus-broker bug as well.