Control: severity -1 serious

I can reproduce the "Failed to check if group polkitd already exists: Connection refused" error in a bullseye VM that is dist-upgraded to bookworm.

systemd v247 before the upgrade listens on /run/systemd/userdb/io.systemd.DynamicUser

once systemd has been upgraded to v252 and reexecd in postinst, systemd no longer listens on this socket.

So, the minimal reproducer is to install a bullseye VM, enable bookworm in /etc/apt/sources.list and run "apt install systemd"

Afterwards, PID 1 no longer listens on the socket.
I assume that something goes wrong during the daemon-reexec causing systemd to reopen the socket.
Any subsequent call to systemd-sysusers then fails.

As shown by #1076506 and the duplicates in the debian forum, I'd say this should be fixed via a stable update.
I'm also bumping this to RC.


A typescript of the minimal reproducer is attached.


Michael


Attachment: typescript
Description: Binary data

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to