Public bug reported:
The latest xenial upload (https://launchpad.net/ubuntu/+source/network-
manager/1.1.93-0ubuntu1) does not start any more under upstart. I
noticed because systemd has an autopkgtest that things still work under
upstart (adt-run --testname cmdline-upstart-boot systemd), and that now
fails. The package diff clearly shows that the upstart jobs got removed.
This is also trivial to reproduce in a xenial VM: install NM, and either
install upstart-sysv or boot with "init=/sbin/upstart".
Note that this does not happen on upgrade, as this does not remove
obsolete conffiles on upgrade:
$ dpkg -s network-manager
[...]
/etc/dbus-1/system.d/nm-ofono.conf f59b8838ed17cfc66de16a977e87a66f obsolete
/etc/init/network-manager.conf 080b2a860317698f65f960687f5363cc obsolete
The package also ships an init script, but does not actually enable it
(dh_installinit), so it does not get run.
Given how late we are in xenial, I suggest to just put back the two
upstart jobs instead of trying to move to the SysV init script.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: i3
Date: Tue Apr 12 09:16:32 2016
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
source-directory interfaces.d
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code
9: Error: nmcli (1.1.93) and NetworkManager (1.0.4) versions don't match. Force
execution using --nocheck, but the results are unpredictable.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code
9: Error: nmcli (1.1.93) and NetworkManager (1.0.4) versions don't match. Force
execution using --nocheck, but the results are unpredictable.
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2:
Error: Object 'nm' is unknown, try 'nmcli help'.
** Affects: network-manager (Ubuntu)
Importance: Critical
Assignee: Martin Pitt (pitti)
Status: Triaged
** Affects: network-manager (Ubuntu Xenial)
Importance: Critical
Assignee: Martin Pitt (pitti)
Status: Triaged
** Tags: amd64 apport-bug regression-release xenial
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Also affects: network-manager (Ubuntu Xenial)
Importance: Critical
Status: Triaged
** Changed in: network-manager (Ubuntu Xenial)
Milestone: None => ubuntu-16.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1569204
Title:
xenial regression: does not start any more under upstart
Status in network-manager package in Ubuntu:
Triaged
Status in network-manager source package in Xenial:
Triaged
Bug description:
The latest xenial upload (https://launchpad.net/ubuntu/+source
/network-manager/1.1.93-0ubuntu1) does not start any more under
upstart. I noticed because systemd has an autopkgtest that things
still work under upstart (adt-run --testname cmdline-upstart-boot
systemd), and that now fails. The package diff clearly shows that the
upstart jobs got removed.
This is also trivial to reproduce in a xenial VM: install NM, and
either install upstart-sysv or boot with "init=/sbin/upstart".
Note that this does not happen on upgrade, as this does not remove
obsolete conffiles on upgrade:
$ dpkg -s network-manager
[...]
/etc/dbus-1/system.d/nm-ofono.conf f59b8838ed17cfc66de16a977e87a66f obsolete
/etc/init/network-manager.conf 080b2a860317698f65f960687f5363cc obsolete
The package also ships an init script, but does not actually enable it
(dh_installinit), so it does not get run.
Given how late we are in xenial, I suggest to just put back the two
upstart jobs instead of trying to move to the SysV init script.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: i3
Date: Tue Apr 12 09:16:32 2016
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
source-directory interfaces.d
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code
9: Error: nmcli (1.1.93) and NetworkManager (1.0.4) versions don't match. Force
execution using --nocheck, but the results are unpredictable.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code
9: Error: nmcli (1.1.93) and NetworkManager (1.0.4) versions don't match. Force
execution using --nocheck, but the results are unpredictable.
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code
2: Error: Object 'nm' is unknown, try 'nmcli help'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569204/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
