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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937866
Title:
network-manager prevents system from halting / rebooting: workaround
is to "stop on runlevel [06]"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/937866/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
