Bug#854814: Fails to start systemd-resolved

[Trevor Bekolay]

On Fri, 10 Feb 2017 18:29:05 +0100 Goran LAZAREVIC <goksibg at gmail.com>
wrote:
> Same bug here, temporary workaroud is to edit :
> /usr/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
> and quote as following :
>
> [Service]
> ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] ||
> echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
> #ReadWritePaths=/run/resolvconf
>
>
> --
> *Goran LAZAREVIC*

I am suffering from the same bug, and can confirm that Goran's workaround
worked for me, except that my resolvconf.conf is located at

/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf

(i.e., not in the /usr directory).

I would consider this is a pretty serious bug since it effectively cut off
my machine from the internet, making it difficult to look up the
workaround. But thanks for the help Goran!

- Trevor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170211/6c96f0de/attachment-0002.html>