[Bug 132434] knetworkmanager after congiguring interface manually, kcmshell takes 100% cpu, also not able to go back to configure automatically

[schmirrwurst at free.fr]

Public bug reported:

Binary package hint: knetworkmanager

I tried to configure my wlan manually, going to "manual configuration"
after that, I wondered there was no way going back to "automatic configuration" or something like that ??

so I went in "manual configuration", and under the wlan interface, I've
delete the current essid, hoping it will go back to automatic
configuration... Then kcmshell was taking 100% from the cpu, after I
kill it, I realised that the changes were made : there was no essid in
manual configuration...

Still, there is a problem with kcmshell or knetwork manager...

Is it normal, not being able to go back to automatic mode ?

** Affects: knetworkmanager (Ubuntu)
     Importance: Undecided
         Status: New

-- 
knetworkmanager after congiguring interface manually, kcmshell takes 100% cpu, also not able to go back to configure automatically
https://bugs.launchpad.net/bugs/132434
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager in ubuntu.