Well, this should have been fixed already with the upload of
0.9.2.0+git201202161854.8572ecf-0ubuntu1; so in theory you would already
have this fix... however, you won't be able to notice this if you've
been carrying that "workaround" for a while.
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.omit.d/.
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.d/sendsigs. You don't need to report all the findings as bugs
immediately, we can work through a possible list when you have the data.
These bug reports will as usual be in /var/crash.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/937866
Title:
network-manager prevents system from halting / rebooting: workaround
is to "stop on runlevel [06]"
Status in “network-manager” package in Ubuntu:
Incomplete
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/network-manager.conf:
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+git201202161854.8572ecf-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
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.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=false
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2011-12-16 (67 days ago)
ftp_proxy:
http_proxy:
mtime.conffile..etc.init.network.manager.conf: 2012-02-21T16:14:41.811524
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected
/org/freedesktop/NetworkManager/Devices/2
usb0 802-3-ethernet unavailable
/org/freedesktop/NetworkManager/Devices/1
eth0 802-3-ethernet unmanaged
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.3.0 connected enabled enabled
enabled enabled disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/937866/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
