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

[Schmirrwurst]

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 ?

[Charlie Figura (cfigura)]

I've seen this as well. I've got a situation where I need to configure as a static IP on one network that I use my laptop on, but need to have the 'automatic' configuration on several others.
I've managed to set up the static IP has a manual configuration, but knetwork manager does not allow (for some reason) any way to reset to automatic.

Here's my workaround:
I copied my /etc/network/interfaces and commented out ALL of the eth1 or eth0 configuration lines and saved the result as /etc/network/clearinterfaces

Then I created a script in my bin directory that just did a
sudo cp /etc/network/clearinterfaces /etc/network/interfaces
sudo /etc/init.d/networking restart

whenever I want to switch to the automatic mode. This seems to work, but it's rather kludgy.