Thank you Michael for the verification. I can confirm this is working as expected as of systemd 245.4-4ubuntu3.14 from (focal-proposed)
slyon@ff:~$ dpkg -l | grep systemd [...] ii systemd 245.4-4ubuntu3.14 amd64 slyon@ff:~$ loginctl list-sessions SESSION UID USER SEAT TTY c2 1001 slyon pts/1
1 sessions listed.
root@ff:~# systemctl restart systemd-logind
slyon@ff:~$ loginctl list-sessions SESSION UID USER SEAT TTY c2 1001 slyon pts/1
The networking after resume issue indeed seems to be unrelated.
Thank you Michael for the verification. I can confirm this is working as expected as of systemd 245.4-4ubuntu3.14 from (focal-proposed)
slyon@ff:~$ dpkg -l | grep systemd
[...]
ii systemd 245.4-4ubuntu3.14 amd64
slyon@ff:~$ loginctl list-sessions
SESSION UID USER SEAT TTY
c2 1001 slyon pts/1
1 sessions listed.
root@ff:~# systemctl restart systemd-logind
slyon@ff:~$ loginctl list-sessions
SESSION UID USER SEAT TTY
c2 1001 slyon pts/1
1 sessions listed.
The networking after resume issue indeed seems to be unrelated.