This bug was fixed in the package nplan - 0.32~16.04.4

nplan (0.32~16.04.4) xenial; urgency=medium

  [ Oliver Grawert ]
  * Prevent unbinding ath6kl_sdio, driver does not support it correctly.
    (LP: #1741910)

  [ Mathieu Trudel-Lapierre ]
  * Re-add snap support patch. (LP: #1747714)
  * Fix syntax for IPv6 addresses in doc. (LP: #1735317)
  * doc: routes are not top-level but per-interface. (LP: #1726695)
  * Implement bridge port-priority parameter. (LP: #1735821)
  * Implement "optional: true" to correctly write systemd network definitions
    with "RequiredForOnline=false", such that these networks do not block boot.
    (LP: #1664844)
  * Various documentation fixes. (LP: #1751814)

 -- Mathieu Trudel-Lapierre <>  Fri, 02 Mar 2018
17:02:03 -0500

** Changed in: nplan (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  network manager snap service name regression

Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in nplan source package in Artful:
  Won't Fix
Status in nplan source package in Bionic:
  Fix Released

Bug description:
  netplan users on Ubuntu Core systems wishing to change netplan configuration 
that affects NetworkManager

  [Test cases]
  1) Run 'sudo netplan apply'
  2) Verify that NetworkManager has been restarted, and no errors were shown on 

  [Regression potential]
  This fixes a current regression where netplan fails to use the right 
NetworkManager service file to restart NM on Ubuntu Core systems. On systems 
with both the NetworkManager from the Ubuntu archive and a snap-based 
NetworkManager are installed, this would default to the snap-based 
NetworkManager. In these cases, existing systems would regress in behavior if 
they have a working installation of NetworkManager from the Ubuntu archive.


  A previous code change seems to have been dropped from nplan on

  The change enabled netplan to restart network-manager service when
  netman is installed as a snap.

  Without the change, netplan tries to restart the debian packaged
  service name of netman.

  Here is the change:

  Please also see customer's fourm post on this topic:

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to