** Description changed: 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. + + [Impact] + + * If a user has both systemd and resolvconf + installed, the networking option in friendly + recovery mode will not work correctly. + + * In this scenario, /etc/resolv.conf will be + empty and dns resolution will not work + + [Test Case] + + * Ensure both systemd and resolvconf are installed + + * Boot to friendly recovery mode and select the + network option from the menu + + * Drop to a root shell by selecting the root shell + option from the menu. + + * `cat /etc/resolv.conf` to make sure it is not + an empty file + + * Run `dig www.google.com` to ensure dns resolution + works properly + + [Where problems could occur] + + * It is possible certain resolvconf or systemd-resolved + configurations could still conflict with each other + + * This would be especially true if a user wanted to use + one nameserver service for a fully booted system and + a different service in friendly recovery mode + + * If the nameserver is misconfigured in resolvconf or + network-manager, it will still be non-functional + in friendly recovery mode.
-- 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
