You say you statically configured an interface using nm-connection-
editor and assigned a nameserver address, and that address did not show
up in the resolvconf-generated resolv.conf file. There is a flaw
somewhere in that chain of events. I believe the flaw is not in
resolvconf so I am reassigning this report to network-manager-gnome, the
package containing nm-connection-editor. In order to get to the bottom
of this it will be very useful if you can reproduce the incorrect
behavior you originally reported.
** Package changed: resolvconf (Ubuntu) => network-manager-applet
(Ubuntu)
** Summary changed:
- /run/resolvconf/resolv.conf contains no nameserver addresses even though the
GUI app was used to configure an interface statically with an associated
nameserver address
+ /run/resolvconf/resolv.conf contains no nameserver addresses even though
nm-connection-editor was used to configure an interface statically with an
associated nameserver address
** Changed in: network-manager-applet (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/999970
Title:
/run/resolvconf/resolv.conf contains no nameserver addresses even
though nm-connection-editor was used to configure an interface
statically with an associated nameserver address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/999970/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
