[GUTSY] NetworkManager eating 100% CPU time

[Uqbar]

Binary package hint: network-manager-kde

Until my last reboot everything was working ok.
Now I am not able to display the NetworkManager icon in the tray anymore and it eats 100% of the cpu.
I have to kill it by hand (sudo killall -9 NetworkManager) in order to have a usable system.

[Serbitar (serbitar-sessionmob)]

same here

[Serkan Hosca (serkan-hosca)]

Same here. sudo /etc/dbus-1/event.d/25NetworkManager restart fixes it. This happened after the upgrade to gutsy.

[Uqbar (uqbar)]

It seems it fixes as my sysyem is not at 100%.
But I still cannot see the friendly icon in the tray showing the connection details.

[Uqbar (uqbar)]

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 shown by Serkan Hosca.

Second.
While NetworkManager is correctly bringing up my ethernet as required, KNetworkManager (v0.2) incorrectly says the cable is unplugged.

[Serkan Hosca (serkan-hosca)]

Doing sudo apt-get remove network-manager --purge && auso apt-get install network-manager fixed the problem for me.

[Uqbar (uqbar)]

When I request to remove the network-manager packages, adept will also remove knetworkmanager and network-manager-kde which
seems to be the be the very same packages as far as versioning is concerned.
But the first one is claimed to be a mere 40KB download, while the second one is 2.1MB.
Reinstalling network-manager won't re-install them. And If I require one of them I'll also get the other one.
And, in any case, the KDE applet is showing a disconnected ethernet even if the interface is up and running.

[Uqbar (uqbar)]

Please, read this:

https://bugs.launchpad.net/bugs/154767

and close this bug.

[deepdraft (dimitar.nedev)]

Sorry, but I do not see the connection between this bug and https://bugs.launchpad.net/bugs/154767 or https://bugs.launchpad.net/ubuntu/+bug/155850. And besides the CONCURRENCY is set to none for me.

The problem of NetworkManager using nearly 100% CPU still persistent under both Gutsy and current alpha Hardy. Only killing and starting it again works as a workaround for me.

[Rapolas K. (casselas)]

It is still in hardy beta, and not only knetwork manager, but also network manager for gnome. Restarting helps..

[deepdraft (dimitar.nedev)]

I am currently running Kubuntu Hardy "development" and for about a month I have not had that problem. Before it used to happen quite frequently - at least once a day.
May be it got fixed by some of the updates.

[Luka Renko (lure)]

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?

[deepdraft (dimitar.nedev)]

I cannot reproduce it with the current version in Hardy.

[Jonathan Thomas (echidnaman)]

Reported fixed.