Control: retile -1 debhelper: Provide way to reload dbus
Simon McVittie:
On Mon, 06 May 2024 at 08:05:55 +0200, Niels Thykier wrote:
I thought the order was sysusers (to create the user) and then tmpfiles (to
create files/directories and set ownership accordingly). In this bug report,
the request is to have the directories first before the user is created.
The request to run tmpfiles before sysusers seems wrong to me, and I think
it should be wontfix. The directories certainly can't be successfully
created owned by the gnome-remote-desktop user before the user even
exists!
My understanding is that the sequence should be:
1. sysusers: Create user
2. tmpfiles: Create home directory owned by that user
3. systemctl daemon-reload
4. Start system services that run as that user
>
[...]
I think the *actual* bug here is that gnome-remote-desktop installs a
D-Bus policy fragment to allow the gnome-remote-desktop user to own the
org.gnome.RemoteDesktop name, but the postinst does not ensure that
the D-Bus system message bus (dbus-daemon or dbus-broker) has reloaded
its configuration before attempting to start gnome-remote-desktop.
I'll follow up to #1070119 with more details since this is not a
debhelper problem.
smcv
Thanks for the feedback. Having read the follow up #1072698, I think we
have a feature request for debhelper which is to support this
interaction between sysusers, tmpfiles, dbus reloading, and (then)
starting the service. Renamed bug accordingly.
Best regards,
Niels
