Bug#968014: systemd 246 postinst script should restart systemd-logind.service
biebl at debian.org
Thu Aug 6 18:39:22 BST 2020
Am 06.08.20 um 19:35 schrieb Zygmunt Krynicki:
> Package: systemd
> Version: 246-2
> Updating systemd to 246-2 leaves systemd-logind.service from 245-* which breaks certain operations.
> One such example is, (assuming user foo): loginctl enable-linger foo. Without restarting systemd-logind.service this command fails with the following error:
> Aug 06 17:08:06 aug061652-827018 systemd-user-runtime-dir: Failed to acquire number of inodes for runtime directory: Unknown interface org.freedesktop.login1.Manager or property RuntimeDirectoryInodesMax.
> Looking at the systemd.postinst script I can see that systemd-logind is not restarted on purpose, referencing upstream systemd bug https://github.com/systemd/systemd/issues/1163. This bug is closed now so I suspect the proper action is to simply restart systemd-logind.service. I've attached a crude patch with that change.
Unfortunately logind can't be restarted safely. Xorg (and Wayland) still
don't handle that properly and crash.
If you want to pursue getting those fixed, this would be very much
welcome. Otherwise I can't really do anything about that in systemd.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers