knetworkmanager 0.2.2 is now available in Hardy and have some fixes that may
help with your problem.
Can all reporters check if you can reproduce this with up-to-date Hardy?
** Changed in: knetworkmanager (Ubuntu)
Assignee: (unassigned) = Luka Renko (lure)
Status: In Progress =
Some more details.
First.
The problem seems to arise actually from the interaction between
KNetworkManager (front end) and the NetworkManager
(back end).
The CPU goes 100% when KNetworkManager is not running or has been
killed/closed. This seems to be fixed by restarting the KNetworkManager as
