KNetworkManager Can't Set "Roaming Mode"

This would probably be a wishlist item.

I have the same problem, and since I installed KUbuntu (and don't wish to install Gnome just to fix this one issue), its a pretty serious problem for me. I have to manually reset the network configuration every time I boot my laptop in order to get it working.

Marking Confirmed because of "I have the same problem".

Possibly related to this: KNetworkManager went into "manual mode", and I can't find any way to turn it back into automatic. The problem is mentioned here:

https://answers.launchpad.net/ubuntu/+source/knetworkmanager/+question/8140

Simpler workaround (doesn't require the full GNOME environment):

1.Install network-manager-gnome
2. Run run nm-applet
3. Tray icon > "Manual Configuration"
4. Click a network, click "Properties"
5. Enable "roaming mode"

No, wait... 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"

It works!

a less invasive workaround for kubuntu users is to:

edit /etc/network/interfaces and comment all lines for the desired interfaces, for example if wlan0 is the interface no more in roaming comment all lines referring to wlan0 in particular line starting with "iface wlan0..."

anyway this bug should be fixed for Hardy!

Added to: https://wiki.kubuntu.org/KubuntuGutsyWhatStillNeedsAConsoleOrAManualConfig

I'll post here the same answer that I wrote at https://answers.launchpad.net/ubuntu/+source/knetworkmanager/+question/8140 :

"I found a workaround: make a backup copy of /etc/network/interfaces , open /etc/network/interfaces 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."

IppatsuMan:
have you read my previous comment? I have already posted this solution.

This is still a problem in my gutsy build, very frustrated with how this is setup.

Another thing is, NetworkManager is so much magic, how does it handle the connection? why couldn't it be just a GUI for /etc/network/interfaces

because I obviously get an address through dhcp, why can't that be in the interfaces file, but instead it produces this thread's bug.
so actually we've got three states now:
-manual
-dhcp
-Networkmanager magic

Unassigning Kubuntu-bugs as it is just a bugmail funnel now.

There isn't a fix available for an SRU, so closing SRU task for Hardy.

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.