[Bug 1891952] Re: systemd-resolved not started when networking enabled

[William Wilson]

This appears to be a conflict between systemd-resolved and resolvconf.

I'm able to recreate the issue with the following steps

1) Fresh 20.04 install

2) boot to friendly recovery
    a) enable networking, drop to root shell
    b) name resolution works as expected

3) reboot to fully booted system and install resolvconf

4) boot to friendly recovery
    a) enable networking, drop to root shell
    b) name resolution no longer works
    c) /etc/resolv.conf is empty
    d) restarting systemd-resolved populates /etc/resolv.conf and name resolution
       begins working again

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/1891952

Title:
  systemd-resolved not started when networking enabled

Status in Release Notes for Ubuntu:
  Fix Released
Status in friendly-recovery package in Ubuntu:
  New
Status in friendly-recovery source package in Groovy:
  New

Bug description:
  I was using friendly-recovery as my Ubuntu desktop session was not
  starting after an upgrade to Groovy Gorilla. When I chose to "Enable
  networking" in the friendly-recovery menu I noticed that no dns
  servers could be reached and come to find out it was because systemd-
  resolved did not start.

  Attached is a photo with some additional information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1891952/+subscriptions