Jsut realised that when I deleted the resolv.conf symlink and instead created a file containing the single line `nameserver 8.8.8.8` in order to get internet access from the broken system, that change remained once I got the system working again. But I forgot to note down what it was pointing to before. I see on my eoan system it's a symlink to `../run/systemd/resolve/stub-resolv.conf` so I presume that's also correct for focal? Just noting it here for other users to remember to fix afterwards (by deleting the file with `cd /etc/`. `sudo rm resolv.conf`, and then `sudo ln -s ../run/systemd/resolve/stub- resolv.conf resolv.conf' (although not sure why it's a relative path and not an absolute one). Searching Google for automatic ways to do this didn't lead me to any more automated way that would work on my focal system which doesn't appear to have the resolvconf package installed.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867431 Title: ERROR got an error from dpkg for pkg: 'libc6' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
