Bug#1065624: resolved not working after installation, race with dbus and user creation

[Michael Biebl]

Am 07.03.24 um 16:22 schrieb Michael Biebl:
> The chain of events afaics is this:
> 
> 1/ postinst creates systemd-resolve
> 2/ systemd-resolved.service is started in postinst
> 3/ dbus trigger is activated after postinst and the dbus config is reloaded
> 
> Because the dbus daemon reload happens after the systemd-resolved user 
> has been created, systemd-resolved could not successfully claim the 
> org.freedesktop.resolve1 D-Bus name.
> 
> What we would need to be able to do is to trigger a dbus daemon-reload 
> after the system user has been created and before the service is started.
> 
> Both is autogenerated code (via dh_installsysusers and 
> dh_installsystemd), and there is no way to inject maintscript code 
> manually unfortunately.

One way to maybe address this is to make dh_installsysusers generate 
maintscript code to reload dbus.
This could either be done unconditionally, via a dh_installsysusers 
option, or automatically when it finds a D-Bus config file shipped by 
the package (and referencing that user).

dh_installsysusers is part of debhelper, so would need to be addressed 
there.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240307/caa03fb9/attachment-0001.sig>