After nearly two months with the fixed version, I think I identified a case were NetworkManager still use 100% CPU and needs to be killed. Here is the step to reproduce :
- hit the Fn+F4 key (= suspend-to-ram shortcut on my thinkpad X40) - while the computer is suspending (blinking 'moon' led), close the lid (= closing the lid is configured to initiate a suspend-to-ram) => upon resume, NetworkManager will hang with 100% cpu. Once hanged, NetworkManager needs to be killed with 'kill -9' and could be restarted (sudo /etc/dbus-1/event.d/25NetworkManager restart), but it will hang again at each subsequent resume from suspend-to-ram. Hope it helps. -- NetworkManager hangs with 100% cpu https://bugs.launchpad.net/bugs/83623 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
