I am trying to verify if I am seeing the same problem or not as reported in this bug. I used to have a network using WEP, but then I changed to WPA-PSK and the connection stopped working. I have, however, found that I can connect to the network by choosing "Connect to other wireless network..." and entering the connection information by hand each time I want to connect. This works fine, but is quite annoying. So far this seems like the same bug as others are having (assuming that "Connect to other wireless network..." works for everyone else as well).
However, I have tried several times completely deleting the existing configuration for that network from gconf (either via the configuration editor or by deleting the corresponding directory in .gconf/system/networking/wireless/networks) and from my keyring (using the Keyring Manager). After a reboot, this makes nm-applet request key information as if it had never heard of the network, so as far as I can tell all old key information should be gone. After entering the key, the connection fails as before with the following message in /var/log/messages: Jan 11 10:42:34 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK' Jan 11 10:42:34 localhost NetworkManager: <info> SUP: response was 'OK' Jan 11 10:42:34 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>' Jan 11 10:42:34 localhost NetworkManager: <info> SUP: response was 'FAIL' Jan 11 10:42:34 localhost NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): real_write_supplicant_config: supplicant error for 'SET_NETWORK 0 psk <key>'. Response: 'FAIL' Therefore, it is having problems with the key. I can still connect by choosing to "Connect to other wireless network...". Unless somewhere I have not thought of there is some residual key information for this connection, this doesn't seem like it is a bug related to my prior WEP configuration. Perhaps this is a separate bug? Are others having the same experience? Can someone duplicate the steps I have taken and see if that solves the problem or not? If others are having the same experience, then could it be that gconf or nm-applet are incorrectly storing the key information in the keyring or gconf and that is the problem? In this case, the fact that people are changing from one security protocol to another would just be coincidental and the real problem would apply generally to all WPA networks. Is this possible? -- [Gutsy] Unable to connect to Access Point if encryption method (WEP/WAP/WAP2) of the AP is changed https://bugs.launchpad.net/bugs/140422 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
