Public bug reported:
Binary package hint: network-manager
NetworkManager hangs the shutdown process for me if connected to a
network.
I rebooted several times, doing nothing but set up the network and then
restarting and each time this was reproducible.
Steps to Reproduce:
1. Set the kernel to boot without the quiet option, so it's possible to see
what's happening (or whichever option it was)
2. Connect computer to wireless
3. Logout -> Restart
The restart hangs at killing NetworkManager.
Pressing the power button at this point makes the process start over, this time
shutting down instead of restarting, and it succeeds in killing NM.
There is a warning between system-tools-backends and NetworkManager (before NM)
about not being able to kill a certain PID because it doesn't exist anymore.
This PID is not that of NM. (Probably some service was already killed and it
was trying to kill it again.) After this, the computer needs to be manually
turned on since it is shutting down instead of restarting.
(Note: on the one time I tried this when I had hibernated in between, pressing
the button didn't work and I had to hold it down and power down without
shutting down cleanly.)
I am running an up-to-date Gutsy install that was updated from Feisty.
Wireless card: ipw3945
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
network-manager fails to stop properly when connected to wireless
https://bugs.launchpad.net/bugs/155216
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
