Bug#1074789: systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser)
Simon McVittie
smcv at debian.org
Wed Jul 3 20:02:58 BST 2024
Control: reassign -1 systemd
Control: retitle -1 systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser)
Control: affects -1 + polkitd
On Wed, 03 Jul 2024 at 19:25:15 +0200, Michael Biebl wrote:
> Am 03.07.24 um 17:15 schrieb Lionel Élie Mamane:
> > $ ls -al /run/systemd/userdb/io.systemd.DynamicUser
> > srw-rw-rw- 1 root root 0 24 mai 17:36 /run/systemd/userdb/io.systemd.DynamicUser
> >
> > $ sudo lsof /run/systemd/userdb/io.systemd.DynamicUser
> > lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc
> > Output information may be incomplete.
>
> systemd should be listening on this socket
>
> At this point, I think it's a systemd issue.
I think it's fairly clear, at least, that this *isn't* a polkitd issue:
its postinst is just using systemd-sysusers in an obvious way, so this
(whatever the underlying issue is here) is going to affect increasingly
many packages as they adopt systemd-sysusers as their way to create their
required system users.
smcv
More information about the Pkg-systemd-maintainers
mailing list