This bug was fixed in the package friendly-recovery - 0.2.42
---------------
friendly-recovery (0.2.42) unstable; urgency=medium
[ Debian Janitor ]
* Trim trailing whitespace.
* Add missing build dependency on dh addon.
* Bump debhelper from old 10 to 12.
* Set debhelper-compat version in Build-Depends.
* Use secure URI in Vcs control header Vcs-Bzr.
[ William 'jawn-smith' Wilson ]
* add resolvconf-pull-resolved.path to script that brings up the
network (LP: #1891952)
-- Dimitri John Ledkov <x...@ubuntu.com> Wed, 27 Jan 2021 15:54:45
+0000
** Changed in: friendly-recovery (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1891952/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
