[Bug 1891952] Re: systemd-resolved not started when networking enabled
Brian Murray
1891952 at bugs.launchpad.net
Mon Aug 31 17:45:03 UTC 2020
Yes, I still observe the issue with systemd 246.2-1ubuntu1. Simply
restarting systemd-resolved populates /etc/resolv.conf and allows name
resolution to work.
** Attachment added: "IMG_20200831_102917.jpg"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5406191/+files/IMG_20200831_102917.jpg
** Changed in: friendly-recovery (Ubuntu Groovy)
Status: Incomplete => New
--
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 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/+source/friendly-recovery/+bug/1891952/+subscriptions
More information about the foundations-bugs
mailing list