Bug#1074789: daemon-rexec no longer reopens /run/systemd/userdb/io.systemd.DynamicUser

[Michael Biebl]

Am 20.07.24 um 17:44 schrieb Michael Biebl:

Am 20.07.24 um 17:40 schrieb Michael Biebl:

Am 20.07.24 um 17:36 schrieb Michael Biebl:

Btw, I vaguely remember successfully testing dist-upgrades of a GNOME installation from bullseye to bookworm. So I suspect this was broken by one of the latest stable updates

Just tested this by upgrading

247.3-7+deb11u4 → 252.6-1 (snapshots.d.o) → systemd listens on the socket after the upgrade 247.3-7+deb11u4 → 252.26-1~deb12u2 (bookworm) → systemd *does not* listen on the socket after the upgrade

Given that these bug reports started popping up only recently, my guess is that it's one of the more recent systemd stable updates like 252.26-1~deb12u2 which regressed.

git bisect shows https://github.com/systemd/systemd-stable/commit/a5fd23650dc as the first faulty commit:

core/varlink: make sure we setup non-serialized varlink sockets

Before this PR, if m->varlink_server is not yet set up during
deserialization, we call manager_setup_varlink_server rather than
manager_varlink_init, the former of which doesn't setup varlink
addresses, but only binds to methods. This results in that
newly-added varlink addresses not getting created if deserialization
takes place.

Therefore, let's switch to manager_varlink_init, and add some
sanity checks to it in order to prevent listening on the same
address twice.


Reverting that fixes daemon-reexec on upgrades.

OpenPGP_signature.asc
Description: OpenPGP digital signature