On Fri, 10 Feb 2017 18:29:05 +0100 Goran LAZAREVIC <[email protected]> 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
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
