Bug#968014: systemd 246 postinst script should restart systemd-logind.service

2020-08-06 Thread Michael Biebl
Am 06.08.20 um 19:41 schrieb Zygmunt Krynicki: >> 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

Bug#968014: systemd 246 postinst script should restart systemd-logind.service

2020-08-06 Thread Zygmunt Krynicki
> 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

Bug#968014: systemd 246 postinst script should restart systemd-logind.service

2020-08-06 Thread Michael Biebl
Control: forcemerge 919509 -1 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.

Bug#968014: systemd 246 postinst script should restart systemd-logind.service

2020-08-06 Thread Michael Biebl
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

Bug#968014: systemd 246 postinst script should restart systemd-logind.service

2020-08-06 Thread 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