More information. This also occurs (and seems to occur more often) after a suspend (for significantly long, like one hour) and seems to be caused by NetworkManager hanging and so it will not respond to a stop command. Also, when this happens, nm-applet is stuck on displaying old information, i.e. I'm still connected to the network I was on before I suspended.
When the latter case happens, running top shows that it is at 100% CPU. I tried to attach a debugger to get a stack trace, but gdb crashed and I did not have pstack installed. The next time this happens, I will try pstack. However, there aren't any symbols in the binary, so I don't know how much use it'll be. My guess is that there are some critical points of NetworkManager's execution that cause it to behave very badly to a stop command and this gets triggered when it's told to shut down at the wrong time. -- 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
