network-manager prevents system from halting / rebooting: workaround is to "stop on runlevel [06]"
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
It appears that my system does not halt correctly (and therefore also does not reboot when asked to do so).
I've came around a fix for this in bug 762203 (comment #93):
The solution / workaround appears to be making network-manager halt on runlevels 0 and 6, and not only when dbus is stopped. Therefore adding the following line to /etc/init/
stop on runlevel [06]
This might indicate some bug with dbus, upstart and/or network-manager.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.2.0+
ProcVersionSign
Uname: Linux 3.2.0-17-
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Tue Feb 21 16:20:04 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
IpRoute:
default via 172.31.216.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
172.31.216.0/24 dev wlan0 proto kernel scope link src 172.31.216.124 metric 2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=false
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2011-12-16 (67 days ago)
ftp_proxy:
http_proxy:
mtime.conffile.
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected /org/freedeskto
usb0 802-3-ethernet unavailable /org/freedeskto
eth0 802-3-ethernet unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.3.0 connected enabled enabled enabled enabled disabled
| Daniel Hahler (blueyed) wrote | #1 |
| Changed in network-manager (Ubuntu): | |
| importance: | Undecided → High |
| summary: |
- network-manager prevents system from halting / rebooting + network-manager prevents system from halting / rebooting: workaround is + to "stop on runlevel [06]" |
| Mathieu Trudel-Lapierre (cyphermox) wrote | #2 |
| Changed in network-manager (Ubuntu): | |
| status: | New → Incomplete |
| Daniel Hahler (blueyed) wrote | #3 |
| Changed in network-manager (Ubuntu): | |
| status: | Incomplete → Fix Released |
| Mathieu Trudel-Lapierre (cyphermox) wrote | #4 |
Well, this should have been fixed already with the upload of 0.9.2.0+
Furthermore, while that change in the upstart job appears to help, it's not a proper fix (because it pretty much reverts to sysvinit behavior, which is precisely what we don't want), so it won't be changed in the network-manager package. The issue actually comes from the fact that NetworkManager should get stopped at the point that it does as per the original upstart job (when dbus ends), but sendsigs will try to kill its subprocesses, which in turn tend to get respawned immediately by NetworkManager. The fix in -0ubuntu1 is supposed to avoid this by registering the wpasupplicant, dhclient, etc. processes in /run/sendsigs.
I'll mark this Incomplete for now, could you please revert your workaround and re-test, along with making sure that any processes that sensigs fails to stop after 60 seconds are caught by apport as bugs -- uncomment the "report_unkillable" function call at line 132 of /etc/init.