Will not connect when manually configuring my wireless connection [Regression]

[Omegamormegil]

Binary package hint: network-manager

Running Ubuntu Hardy alpha with all updates as of right now. When attempting to turn off roaming, and configure my wireless network connection manually through the network-manager, I can not get connected. I am able to fill in all the connection information: my WPA Personal key, selecting my SSID from the list, and setting my IP address to static. I can close the network manager successfully, and it all appears to have worked - my processor jumps to 100% for a few seconds. After doing this, the signal strength meter on my panel becomes a black monitor, which provides me with no connection information - the connection information option in the right click menu is gray. I am not connected to my network.

If I click the network-manager applet, go back to the manual configuration option, and turn Roaming Mode back on in network-manager, and leave network manager, I get my signal strength meter back on my panel and it indicates I am connected to my wireless network at 68%. Even this is inconsistent, but it will let me connect (I've entered this as a separate bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/201081). The only way I can get connected and stay connected is to configure network-manager to use roaming mode, and to restart my computer. After Ubuntu boots up, I fill in my keyring password and it will stay connected.

This is a regression, as before upgrading to Hardy, this was how I would always connect to my wireless network, to avoid having to fill in my default keyring password every time I start Ubuntu (as is required when using roaming mode).

[Alexander Sack (asac)]

please try to configure your network manually and if you finished that and are in the state with the black monitors and no connection listed in network-manager, please open a terminal and run:

 sudo ifdown eth0 (replace this with the device name that you configured)
 sudo ifup eth0

are you connected afterwards?

 - Alexander

[Omegamormegil (omegamormegil)]

Yes, what you suggested will actually cause my manual setup to connect me to my network.

I seem to have discovered something else which will cause this to work. I have repeated the steps 5 or 6 times, and it is a repeatable situation. The exact steps are important: Enter network manager, click Unlock, enter password and hit enter, click to select wireless connection, click properties, uncheck enable roaming, fill in the fields, click Close button. At this point I am returned to the previous screen, as my processor usage jumps to 100. Here is the important step. If, as soon as I am able, I click close to exit the network-manager, my connection to the network will not work. However, I've noticed that if instead of clicking Close, I click back into the box to re-select my wireless connection for example, and then click the Close button, the connection WILL work.

[Omegamormegil (omegamormegil)]

nate@Numenore:~$ ping 192.168.1.1
connect: Network is unreachable
nate@Numenore:~$ sudo ifdown eth1
[sudo] password for nate:
ifdown: interface eth1 not configured
nate@Numenore:~$ sudo ifup eth1
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - * Starting portmap daemon...
 * Already running.
   ...done.
 * Starting NFS common utilities
   ...done.
nate@Numenore:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.47 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.25 ms

--- 192.168.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 1.255/1.366/1.477/0.111 ms
nate@Numenore:~$

[Pēteris Krišjānis (pecisk-gmail)]

Smells like duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/185854

And it is g-s-t, which does manual configuration :)