The issue is fixed in Ubuntu 17.10, it's not likely to get SRUed to the
previous stable now though
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification beca
The attachment "Port of patch from Patch from
https://bugzilla.gnome.org/show_bug.cgi?id=779087 to network-manager
1.4.4-1ubuntu3.1" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsub
~jonathanharker could you check if `nmcli connection show 'CONNECTION
NAME' | grep DNS` shows the nameservers you expect? You can list
connection names with `nmcli connection`. This way we'll make sure if
the problem happens between NM and the VPN or NM and resolved (for me it
was the latter, and t
There is a fix posted on the upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=779087 - I've attached a
ported patch.
** Bug watch added: GNOME Bug Tracker #779087
https://bugzilla.gnome.org/show_bug.cgi?id=779087
** Patch added: "Port of patch from Patch from
https://bugzilla.gnome.org
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691996
Tit
The DNS for the tun0 of my OpenVPN connection completely fails. There's nothing
in systemd-resolve --status or /var/run/resolv.conf or /etc or any of the other
usual places; I don't have time to go digging so I shove stuff in /etc/hosts
for now.
Pretty useless state of affairs, all told...
--
