Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#968014: systemd 246 postinst script should restart systemd-logind.service
33 views
Skip to first unread message
Zygmunt Krynicki
Aug 6, 2020, 1:40:03 PM8/6/20
to
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[28557]: 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.
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[28557]: 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.
Zygmunt Krynicki
Aug 6, 2020, 1:50:03 PM8/6/20
to
> 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.
I see, this is quite unfortunate.
Could the postinst script refer the current set of blocking issues?
Could the postinst script restart logind if neither X nor wayland is employed? In my configuration it is really affecting CI systems that are all headless.
Best regards
ZK
> 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.
I see, this is quite unfortunate.
Could the postinst script refer the current set of blocking issues?
Could the postinst script restart logind if neither X nor wayland is employed? In my configuration it is really affecting CI systems that are all headless.
Best regards
ZK
Michael Biebl
Aug 6, 2020, 1:50:03 PM8/6/20
to
Am 06.08.20 um 19:35 schrieb Zygmunt Krynicki:
Michael
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.
Regards,
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.
Michael
0 new messages