How to switch back to automatic mode?

I would like to confirm this problem, I, also, tried to uninstall + reinstall but to no avail.

oh no! That wasn't supposed to be an answer... moderators, please note that this has not been resolved.

Is there any response to this????? I have been trying to manage my way around the issue for the last week or so, and no really result...

Switched to KwifiMan. but it seems to not work especially well either.

No, reinstallation of Knetworkmanager did not solve my problem. Only reinstall of whole Kubuntu helped...

I'm having the same problem and found this bug in the bug database:

https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/125767

It mentions that the only way to currently fix this is to log into Gnome and fix it with nm-applet, which isn't a great option for me since it means installing enough of Gnome to do so. :\

Workaround: install network-manager-gnome (not the whole GNOME environment), then run run nm-applet. Left-click the tray icon, go to "Manual Configuration", and then you can pick a network's properties and enable "roaming mode".

No, wait, it's even simpler! nm-applet just runs network-admin, so:

1. Install gnome-system-tools
2. Run "sudo network-admin"
3. Click a network, click "Properties"
4. Enable "roaming mode"

Note: this isn't a fix for the bug (see Bug #125767 for that), but it is a workaround that should get you back on track.

I found a workaround: make a backup copy of /etc/network/interfaces , open it as root with your favourite text editor and edit it:

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

comment out any other line with a #. Restart KDE and KNetworkManager will (hopefully) work fine again.

I can confirm that IppatsuMan's fix worked for my kubuntu install :D
required only the edit and a reboot
many thanks

IppatsuMan's fix worked for me, too. Now why can't something as simple as this be incorporated into KNetworkManager? Would this break some installations? Is it because manual fixes would be lost? The wallet remembers the information that are saved from roaming mode, even after IppatsuMan's fix.

I created a file interfaces.repair with IppatsuMan's file, to just cp in case I somehow end up back in manual mode again.

Unfortunately this ist only a "work-around" but NOT EVEN CLOSE to a solution.

It can not be this tricky to get a simple wireless lan selector going. By hand manipulation and a reboot is no solution, it's a pain. Also, I am very unhappy with this fact for the simple reason that I have a fixed IP (manual config) at work, but would like to use wlan at home (I know thousand other ways to do this, but a default solution - as knetworkmanager - has to work FROM START).

Hopefully somebody will finally overcome this silly problem in the near future.

IppatsuMan's fix worked, but I wanted to be able to set it up with my home WEP key ( why I am in trouble in the first place)

Jon Anderson's fix did not work:
I got the following errors:
foo@foo~$ sudo network-admin
(network-admin:8914): Gtk-WARNING **: Unknown property: GtkComboBox.items
** (network-admin:8914): CRITICAL **: Unable to lookup session information for process '8914'

Thanks!

dlebauer: sudo is for shell commands, as network-admin uses X you should try:

foo@foo~ $ kdesu network-admin