Thanks for the additional details!
In this case the output of "resolvectl" after "netplan apply" and after
resume (no "netplan apply") might be useful. In addition to debug-logs
of your systemd-resolved
$ sudo systemctl edit systemd-resolved
Adding:
```
[Service]
Environment=SYSTEMD_LOG_LEVEL=d
As far as I know I am not using NetworkManager, 'nmcli dev' shows the
following:
DEVICE TYPE STATE CONNECTION
virbr0 bridgenem kezelt --
vm-br0 bridgenem kezelt --
lan ethernet nem kezelt --
lo loopback nem kezelt --
iscsi
Are you using NetworkManager in parallel here? Could you please provide
the output of `nmcli dev`? The applications you mention (App Store,
Settings/Online Accounts,...) seem to be Desktop centric and might rely
on NetworkManager functionality for the connectivity checker, which
systemd-networkd mi
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060778
Title:
netplan, multiple dhcp route with metric failure
To manage