The default of not restarting systemd-logind as it ends graphical sessions (in all cases I've tested) seems reasonable.
Having it detect a non-GUI system and restart in that case wouldn't be unreasonable. People who REALLY want to restart daemons on update should have needrestart installed as nothing less will cover the case of upgrading security related libraries that are used by externally facing daemons (EG SSL libraries). The needrestart package defaults to not restarting systemd-logind but when run from "apt upgrade" provides a user interface to allow selecting to do it. https://lists.debian.org/debian-security-announce/2019/msg00008.html As an aside the systemd update that inspired this bug had fixes for "a memory leak in systemd-journald" and "an unrelated bug in systemd-coredump" which shows that for most users that bug wouldn't require restarting systemd-logind. Should this bug be closed wih "can be fixed by installing needrestart"? -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
