[FFE] NetworkManager 1.2-beta

Bug #1552424 reported by Mathieu Trudel-Lapierre
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Undecided
Mathieu Trudel-Lapierre
network-manager-applet (Ubuntu)
Fix Released
Undecided
Mathieu Trudel-Lapierre
network-manager-iodine (Ubuntu)
Fix Released
Undecided
Mathieu Trudel-Lapierre
network-manager-openconnect (Ubuntu)
Fix Released
Undecided
Mathieu Trudel-Lapierre
network-manager-openvpn (Ubuntu)
Fix Released
Undecided
Mathieu Trudel-Lapierre
network-manager-pptp (Ubuntu)
Fix Released
Undecided
Mathieu Trudel-Lapierre
network-manager-vpnc (Ubuntu)
Fix Released
Undecided
Mathieu Trudel-Lapierre

Bug Description

We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release.

This new release will also much improve interop with LXC, which has recently been an issue.

Other FFEs will be opened for NM VPN plugins and for NetworkManager-applet.

----
============================================
NetworkManager-1.2
Overview of changes since NetworkManager-1.0
============================================

This is a new stable release of NetworkManager. Notable changes include:

* Added an option to enable use of random MAC addresses for Wi-Fi access
    point scanning (defaults to disabled). Controlled with
    'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in
    ifcfg files).
* Wi-Fi scanning now utilizes wpa_supplicant's AP list.
* Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg
    files.
* Added support for creation of more types of software devices: tun & tap,
    macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6).
* The software devices (bond, bridge, vlan, team, ...) can now be stacked
    arbitrarily. The nmcli interface for creating master-slave relationships
    has been significantly improved by the use of 'master' argument to
    all link types.
* RFC7217 stable privacy addressing is now used by default to protect from
    address-based host tracking. The IPv6 addressing mode is configured with
    IPV6_ADDR_GEN_MODE key in ifcfg files.
* Improved route management code to avoid clashes between conflicting
    routes in multiple connections.
* Refactored platform code resulting in more robust interface to platform,
    less overhead and reduced memory footprint.
* Improved interoperability with other network management tools. The
    externally created software devices are not managed until they're
    activated.
* The Device instances now exist for all software connections and the platform
    devices are now only created when the device is activated. This makes it
    possible for connections with device of same name not to clash unless
    they're activated concurrently. The links are now not unnecessarily present
    unless the connection is active, avoiding pollution of the link namespace.
* NetworkManager now correctly manages connectivity in namespace-based
    containers such as LXC and Docker.
* Support for configuring ethernet Wake-On-Lan has been added.
* Added LLDP listener functionality and related CLI client commands. Enabled via
    LLDP option in ifcfg files.
* CLI secret agent has been extended with support for VPN secrets.
* The command line client now utilizes colors for its output.
* The command line client now sorts the devices and properties for better
    clarity.
* Numerous improvements to Bash command completion for nmcli.
* NetworkManager relies on less external libraries. The use of dbus-glib
    has been replaced with gio's native D-Bus support and libnl-route is no
    longer used.
* Dependency on avahi-autoipd has been dropped. Native IPv4 link-local
    addressing configuration based on systemd network library is now used
    instead.
* Hostname is now managed via systemd-hostnamed on systemd-based systems.
* Management of resolv.conf management can be changed at runtime, private
    resolv.conf is always written in /run.
* NetworkManager can now write DNS options to resolv.conf.
* Updated version of systemd network library used for internal DHCP and
    IPv4 link-local support.
* Support for event logging via audit subsystem has been added.
* Support for native logging via systemd-journald has been added taking
    advantage of its structured logging.
* Live reconfiguration of IP configuration after changing the settings without
    reactivation of the device with "nmcli device reapply" command and via
    D-Bus API.
* The API for VPN plugins now supports multiple simultaneous connections.
    Most popular VPN plugins have been updated to support this functionality.
* The libnm library now provides API to access VPN service definitions.
* New DHCP_FQDN key in ifcfg files to configure the full FQDN to be sent to
    the DHCP servers.
* The timeout for DHCP requests can now be modified using the
    'ipv4.dhcp-timeout' property.
* Added multicast_snooping option to BRIDGING_OPTS ifcfg key.
* Added support for detecting duplicate IPv4 addresses, with a timeout
    configurable through the ipv4.dad-timeout connection property.
* Fixed a race condition that could potentially lead to unauthorized access
    to connection secrets (CVE-2016-0764).
* dnsmasq configuration for shared connections can now be extended by
    placing custom files in /etc/NetworkManager/dnsmasq-shared.d/.
* Generic devices are no longer assumed unless explicitly requested by
    user.
* The reorder-header VLAN flag setting is now honored; to keep backwards
    compatibility in behavior, an existing REORDER_HDR=0 ifcfg-rh key is
    ignored; the flag must be disabled with VLAN_FLAGS=NO_REORDER_HDR.
* Fair amount of bugs was fixed and robustness was generally improved.

The following features were backported to 1.0.x releases from 1.0.0 to 1.0.8
are also present in NetworkManager-1.2:

* Added support for handling VPN secrets to nmtui and nmcli agent.
* The team devices can now properly be enslaved to bridges.
* Failed DHCP attempts for assumed connections are now retried after
    a timeout.
* Default wired connection is now created after udev registers the device.
* Support for Bluetooth DUN devices with Bluez 5 has been fixed.
* The 'ipv6.ignore-auto-dns' property is now properly honored making it
    possible to override automatically obtained name servers.
* Invalid permanent MAC addresses as reported by some devices are now
    ignored.
* Device links reported by more recent versions of Linux kernel that reside
    in different network namespaces are no longer confused with links in
    the namespace NetworkManager runs in.
* MAC address changes of bond or team devices are now properly propagated
    to VLANs created on the device.
* Fixed error handling for teaming devices with invalid configuration.
* Wi-Fi AP list is now updated correctly after AP mode has been used.
* The error handling for VPN secret agents is now significantly more robust.
* Detection of s390 CTC devices now works properly.
* A GATEWAY key in in /etc/sysconfig/network now no longer affects
    non-static connections.
* Added support for IPv6-only VPN connections.
* The systemd service now uses HUP signal to reload configuration.
* Change VLAN default flags to set REORDER_HDR for new connections.
* nmtui is now able to ignore automatically configured routes.
* Allow setting IPv6 and PPP settings for GDM and CDMA connections via
    nmcli.
* Added support for adding ADSL connections in nmcli.
* Improved capture portal detection.
* Default route through WiFi connection is now preferred to Mobile
    Broadband if both are available.
* Expose a flag to determine whether a particular connection is metered
    via API and client tools. Configurable in ifcfg with CONNECTION_METERED
    key.
* Add support for locking connections to a channel within a particular
    band.
* Add support for configuring Wake-on-LAN capabilitites.
* Allow overriding the MTU for team device.
* The MTU setting from an IPv6 neighbor discovery Router Advertisements is
    now ignored if applying it would result in invalid configuration.
* Some configuration options can now be changed without restarting the
    daemon. Notably, this applies to 'dns', 'connectivity' and
    'ignore-carrier' settings.
* The connection activation was made more robust. If an active connection
    is reactivated, the device it is active on takes precedence. If an attempt
    is made to activate a connection on a different device than the one it is
    active on, the activation proceeds removing the connection from the active
    device.
* The device specifiers in configuration files now support negation via
    'except:' match.
* Devices that only have IPv6 link-local address are no longer assumed to
    be connected.
* nmcli now provides hints and tab-completion for enumeration properties.
* If the IPv6 interface tokens are set they are honored when creating an
    interface identifier for IPv6 addressing.
* NetworkManager now maintains correct routing configuration when multiple
    interfaces are connected to the same network.
* The management of devices can now be controlled with udev rules. The veth
    devices as well as the virtual Ethernet devices of various
    virtualization tools (VMWare, VirtualBox, Parallels Workstation) are
    now ignored by default.
* The IPv6 privacy extensions are now enabled by default and handling of
    the ip6-privacy sysctl has been improved.
* Activating a Bond, Bridge or Team device can now optionally activate the
    slave connections as well. The behavior is controlled with
    'connection.autoconnect-slaves' property and AUTOCONNECT-SLAVES key in
    ifcfg files.
* The platform support code has been refactored, resulting in better
    scalability in large configurations.
* Changes to network interfaces configuration done outside NetworkManager
    are now picked up and exposed to the user via NetworkManager API and tools.
* A connection can now optionally leave externally configured default route
    in place instead of overriding it. The behavior is controlled with
    'ipv4.never-default' and 'ipv6.never-default' properties.
* nmcli allows multiple devices for 'nmcli device disconnect/delete'.
* Firewall zone is added to firewalld for device-based VPN connections too.
* Wi-Fi devices now indicate support for 2GHz and 5GHz frequencies
* "nmcli device" output now indicates physical port ID
* New config items added to the 'ifcfg-rh' plugin:
  - IPV4_ROUTE_METRIC and IPV6_ROUTE_METRIC
  - DEVTIMEOUT
  - IPADDR and PREFIX are now supported for specifying address ranges of
      shared IPv4 connections
* Dispatcher scripts now get a CONNECTION_FILENAME variable with the path
    to the configuration file for the connection
* An example dispatcher script that is able to apply complex routing rules
    (such as setting up policy-based routing) for 'ifcfg-rh' connections was
    added to examples/dispatcher/.
* 'mode' key of Bond device options property now accepts numeric values
* Connection attempts for devices without carrier on startup now wait for
    carrier to appear within a short timeout instead of failing
    immediately. This makes system startup more robust.
* Bridge connectivity is now properly restored on resume from suspend
* The D-Bus name is acquired earlier during the daemon startup. This makes
    it possible for the systemd service manager to optimize the service
    startup so that services that require networking are activated sooner
    contributing to faster system start up time.
* A lot of memory leak problems were fixed, resulting in reduced memory usage.
    Many of them were discovered as a result of improvements in use of
    Valgrind in the testing infrastructure.
* Management of 'teamd' daemon instances for Team devices is now more robust.
* The 'dnsmasq' daemon respawns when it terminates and it is configured for
    management of DNS resolver configuration
* Hostnames that are not fully qualified are no longer sent to a DHCPv6
    server for a dynamic DNS update
* Connection UUIDs are now checked for uniqueness when connection
    configurations are read
* Receipt of a NDP Router Advertisement can no longer lower the IPv6 hop
    limit (CVE-2015-2924)

Revision history for this message
Stéphane Graber (stgraber) wrote :

Is Network Manager 1.2 out yet? I don't seem to remember seeing an announcement.

If not, when is it expected to be out?

Also, can you comment on our existing delta (phone & others) and give some more details on how those will be updated and tested?

Overall, I absolutely support us moving to 1.2, it does fix a lot of pain points that I've encountered in the past and I'm sure it would greatly benefit our users. But we need to make sure landing this won't cause regressions and that we'll ship with a properly supported NM by release time.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

It's not out yet; I'm trying to find out the roadmap but given that it's beta right now, I expect it to be ready in time for release.

Our delta against Debian is limitted to some specific decisions we've made (priority of devices, enabling some feature or another), and the addition of support for oFono.

Indeed, it's not a risk-free update given the scope and the impact on desktop and our users, it will need to be very much tested.

Revision history for this message
Lorn Potter (lorn-potter) wrote :

awe is currently working on getting the update to 1.2 working. Work is ongoing, and needs a few more improvements and patches ported.

Revision history for this message
Martin Pitt (pitti) wrote :

> Other FFEs will be opened for NM VPN plugins and for NetworkManager-applet.

I suspect that they need to be updated in lockstep, so perhaps better just add tasks here? Or are they really independent from updating NM itself?

I generally support this as well, but this needs loads of testing across devices that we have. With that I'm interested in a contingency plan, i. e. at this point I'd like to make sure that in the worst case we can roll back. Which other packages would this upgrade affect aside from network-manager{,-vpn,-applet}?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

The SUSE release manager asked in nm about releasing before May1st. Plan is for rc1 in about 2 weeks or less.
https://mail.gnome.org/archives/networkmanager-list/2016-March/msg00108.html

In the past we have included some key projects beta or rcs and then SRUed the final version in. Could this be a candidate for that instead of creating a contingency plan for it not releasing before 16.04 release day?

Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

NM developers already said the final 1.2 release will be close enough to 1.2-beta2 or master.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager-applet (Ubuntu):
status: New → Confirmed
Changed in network-manager-openconnect (Ubuntu):
status: New → Confirmed
Changed in network-manager-openvpn (Ubuntu):
status: New → Confirmed
Changed in network-manager-pptp (Ubuntu):
status: New → Confirmed
Changed in network-manager-vpnc (Ubuntu):
status: New → Confirmed
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Build logs are available for each of the packages from my PPA: https://launchpad.net/~cyphermox/+archive/ubuntu/nm/+packages:

https://launchpadlibrarian.net/250334184/buildlog_ubuntu-xenial-amd64.network-manager_1.1.91-0ubuntu1~mtrudel1_BUILDING.txt.gz
https://launchpadlibrarian.net/250458101/buildlog_ubuntu-xenial-amd64.network-manager-applet_1.1.91-1ubuntu1~mtrudel1_BUILDING.txt.gz

VPN plugins are all simple sync from Debian unstable (we drop Ubuntu changes which were only there for convenience), except for network-manager-openconnect, which is an update to the package.

We'll still need to update to 1.2 final once it's released (should be incessantly).

Changed in network-manager-iodine (Ubuntu):
status: New → Confirmed
Changed in network-manager-applet (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Changed in network-manager-iodine (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Changed in network-manager-openconnect (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Changed in network-manager-openvpn (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Changed in network-manager-pptp (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Changed in network-manager-vpnc (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Changed in network-manager (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Thanks Mathieu.

1.1.92 (1.2-beta3) was just released yesterday.

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

@Mathieu
Tried the PPA. The Canonical VPN doesn't work for me. It says it connects, but then I can't access anything on the net or VPN. Reverting it, and its working again. A few times the nm-applet has also crashed when I do this. - Should I open a new bug for these issues?

Revision history for this message
Tony Espy (awe) wrote :

@Bryan

Thanks for the test results.

Let's not open any new bugs for now, as Mathieu was able to reproduce the Canonical VPN issue and noticed that the problem is probably related to the dnsmasq DBus changes that were made as part of the upgrade to NM1.2. I'll take a look at this later today and see if I can reproduce.

Regarding the applet crash, could you add a backtrace to the bug for us? I'll also see if I can reproduce.

Finally, in discussing with Mathieu, one other issue exists with the applet icons when VPN is enabled. This is probably due to an icon path mismatch.

As @Amr mentioned in comment #14, 1.1.92 ( beta3) was released last week. I'm currently testing this version for Touch. The final release of NM1.2 is expected to land this week.

Revision history for this message
Bryan Quigley (bryanquigley) wrote :

@Tony, Previously all I tried was connecting/disconnecting from the VPN and the applet eventually crashed. Couldn't reproduce it in this go around. (I'm guessing that with working VPN it might not occur)

Revision history for this message
Tony Espy (awe) wrote :

@Bryan

Thanks for the reply.

I actually did a fresh xenial install on my Thinkpad 410s this afternoon, installed the packages from Mathieu's PPA, and then configured the Canonical VPN. I'm able to start it, but once active, I'm not also not able to access the network. This is most likely a bug in the updated dnsmasq code as after the VPN is started, dnsmasq is left without any DNS servers configured ( you can check this by sending SIGUSR1 to dnsmasq and checking the syslog output ).

Also, Mathieu mentioned that when the VPN is activated, the WiFi icon shown by the applet is incorrect. I see just the small lock, and no signal bars. This is probably due to a path issue with the icons in the applet.

No applet crashes on my end.

Revision history for this message
Tony Espy (awe) wrote :

The openvpn failure to setup DNS is due to an error returned to the DBus call to dnsmasq:

dnsmasq update failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid IP address: 'buildd': bad address

So, pretty sure this is a bug in the patch [1] that adds DBus support to dnsmasq, and that the domain and IP address are getting mixed up.

[1] 0001-dns-use-DBus-to-make-dnsmasq-nameserver-changes.patch

Revision history for this message
Tony Espy (awe) wrote :

The openvpn failure is actually a symptom of a larger problem which can affect *any* DNS server ( ie. not just servers associated with a VPN ) that includes a domain. The updated gdbus patch mentioned in the previous comment adds the DBus parameters to the dnsmasq SetServersEx method in the wrong order when a domain is specified, domains are actually supposed to come *after* the IP address of a nameserver:

+static void
+add_dnsmasq_nameserver (NMDnsDnsmasq *self,
+ GVariantBuilder *servers,
+ const char *ip,
+ const char *domain)
+{
+ g_return_if_fail (ip);
+
+ _LOGD ("adding nameserver '%s' for domain '%s'",
+ ip, domain);
+
+ g_variant_builder_open (servers, G_VARIANT_TYPE ("as"));
+
+ if (domain)
+ g_variant_builder_add (servers, "s", domain);
+ g_variant_builder_add (servers, "s", ip);
+
+ g_variant_builder_close (servers);
+}

Fixing is just a matter of moving the "if (domain)" statement to after the g_variant_build_add call for the servers.

See the following page for a description of the dnsmasq DBus interface:

http://www.thekelleys.org.uk/dnsmasq/docs/DBus-interface

Revision history for this message
Tony Espy (awe) wrote :

NM 1.1.93 ( 1.2-rc1 ) was just released.

Revision history for this message
Tony Espy (awe) wrote :

I've re-based Mathieu's branch on rc1:

lp:~awe/network-manager/update-1.2

I've pushed a version to my PPA:

https://launchpad.net/~awe/+archive/ubuntu/ppa

The original issue ( no DNS ) seen with the Canonical VPN seems to have been resolved, although the behavior seems to be slightly different than 1.0.4x( wily ) which appears to add the VPN DNS server vs. replace the existing nameservers. Mathieu says this is by design, however I don't feel like its totally understood yet.

Revision history for this message
Tony Espy (awe) wrote :

OK, strike the last bit about nameservers being added vs. replaced. I was the one who misunderstood how the VPN IPv4v6 dialogs work, and thus wasn't finding the "User this connection only for the resources on this network" checkbox. Once I did, the VPN DNS works as expected.

Revision history for this message
Stéphane Graber (stgraber) wrote :

Okay, lets do this then. FFe granted. Given how critical NM is, I expect you to be taking a very very close look at any bug reports and IRC chatter following this change and very quickly upload fixes as needed until release time so the final delta between what we ship at release time and final 1.2 is minimal.

Changed in network-manager (Ubuntu):
status: Confirmed → Triaged
Changed in network-manager-applet (Ubuntu):
status: Confirmed → Triaged
Changed in network-manager-iodine (Ubuntu):
status: Confirmed → Triaged
Changed in network-manager-openconnect (Ubuntu):
status: Confirmed → Triaged
Changed in network-manager-openvpn (Ubuntu):
status: Confirmed → Triaged
Changed in network-manager-pptp (Ubuntu):
status: Confirmed → Triaged
Changed in network-manager-vpnc (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Harm van Bakel (hvbakel) wrote :

I tried the nm packages in the proposed repositories and I'm experiencing crashes in nm-pptp-ppp-plugin:

Apr 10 13:33:46 xps-9343 NetworkManager[778]: <info> [1460309626.6913] audit: op="connection-activate" uuid="0c424828-8229-4ceb-acfd-237b46648424" name="VPNtest" pid=1869 uid=1000 result="success"
Apr 10 13:33:46 xps-9343 NetworkManager[778]: <info> [1460309626.6947] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: Started the VPN service, PID 21714
Apr 10 13:33:46 xps-9343 NetworkManager[778]: <info> [1460309626.7058] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: Saw the service appear; activating connection
Apr 10 13:33:46 xps-9343 NetworkManager[778]: <info> [1460309626.7104] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state changed: init (1)
Apr 10 13:33:46 xps-9343 NetworkManager[778]: <info> [1460309626.8098] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN connection: (ConnectInteractive) reply received
Apr 10 13:33:47 xps-9343 NetworkManager[778]: ** Message: pppd started with pid 21723
Apr 10 13:33:47 xps-9343 NetworkManager[778]: <info> [1460309627.7636] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state changed: starting (3)
Apr 10 13:33:47 xps-9343 pppd[21723]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Apr 10 13:33:47 xps-9343 NetworkManager[778]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Apr 10 13:33:47 xps-9343 NetworkManager[778]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing
Apr 10 13:33:47 xps-9343 NetworkManager[778]: (process:21723): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 'g_variant_is_object_path (object_path)' failed
Apr 10 13:33:47 xps-9343 kernel: [72071.405574] pppd[21723]: segfault at 8 ip 00007fd0b43feb0c sp 00007ffe051b47f0 error 4 in nm-pptp-pppd-plugin.so[7fd0b43fd000+3000]
Apr 10 13:33:47 xps-9343 NetworkManager[778]: ** (nm-pptp-service:21714): WARNING **: pppd died with signal 11
Apr 10 13:33:47 xps-9343 NetworkManager[778]: <warn> [1460309627.8919] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: failed: connect-failed (1)
Apr 10 13:33:47 xps-9343 NetworkManager[778]: <info> [1460309627.8921] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state changed: stopping (5)
Apr 10 13:33:47 xps-9343 NetworkManager[778]: <info> [1460309627.8922] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state changed: stopped (6)
Apr 10 13:33:47 xps-9343 NetworkManager[778]: <info> [1460309627.8930] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN plugin: state change reason: unknown (0)
Apr 10 13:33:47 xps-9343 NetworkManager[778]: <info> [1460309627.8943] vpn-connection[0xe737d0,0c424828-8229-4ceb-acfd-237b46648424,"VPNtest",0]: VPN service disappeared

Revision history for this message
Sebastien Bacher (seb128) wrote :

@Harm, could you get a backtrace (https://wiki.ubuntu.com/DebuggingProgramCrash) of the issue?

Revision history for this message
Harm van Bakel (hvbakel) wrote :

@seb128, I just submitted Bug #1569022 that contains a backtrace of the crash.

Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Should this bug be closed?

Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Fixed in yakkety.

Changed in network-manager (Ubuntu):
status: Triaged → Fix Released
Changed in network-manager-applet (Ubuntu):
status: Triaged → Fix Released
Changed in network-manager-openconnect (Ubuntu):
status: Triaged → Fix Released
Changed in network-manager-openvpn (Ubuntu):
status: Triaged → Fix Released
Changed in network-manager-pptp (Ubuntu):
status: Triaged → Fix Released
Changed in network-manager-vpnc (Ubuntu):
status: Triaged → Fix Released
Changed in network-manager-iodine (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Oops! iodine is not fix released! It's still 1.1.0.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.