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

[William Wilson]

Attached is a patch to SRU focal.

** Patch removed: "lp1891952_hirsute.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457117/+files/lp1891952_hirsute.debdiff

** Patch removed: "lp1891952_groovy.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457119/+files/lp1891952_groovy.debdiff

** Patch removed: "lp1891952_focal.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457120/+files/lp1891952_focal.debdiff

** Patch added: "lp1891952_focal.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457122/+files/lp1891952_focal.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
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