Ok Maybe not quite fixed yet. I experinced this problem when I first tested 0.6.6-0ubuntu5 though I was not able to replicate it again until now.
Vary rarely on a reconnect (ie a successfull connection was made, then disconnect occurred) it seems that AP_SCAN 1 is being used. Apr 6 07:26:39 pug NetworkManager: <info> Supplicant state changed: 0 Apr 6 07:28:18 pug NetworkManager: <info> Activation (wlan0) started... Apr 6 07:28:18 pug NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Apr 6 07:28:18 pug NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Apr 6 07:28:18 pug NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Apr 6 07:28:18 pug NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Apr 6 07:28:18 pug NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Apr 6 07:28:18 pug NetworkManager: <info> Activation (wlan0/wireless): access point 'ferguson-home' is encrypted, and a key exists. No new key needed. Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant0^I' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was 'OK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'AP_SCAN 1' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was 'OK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'ADD_NETWORK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was '0' Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 6665726775736f6e2d686f6d65' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was 'OK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was 'OK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was 'OK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was 'OK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 pairwise TKIP' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was 'OK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 group TKIP' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was 'OK' Apr 6 07:28:20 pug NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Apr 6 07:28:20 pug NetworkManager: <info> SUP: response was 'OK' Apr 6 07:28:20 pug NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Apr 6 07:28:25 pug avahi-daemon[5517]: Registering new address record for fe80::214:a4ff:fe60:fbe7 on wlan0.*. Apr 6 07:29:20 pug NetworkManager: <info> Activation (wlan0/wireless): association took too long (>60s), failing activation. -- Gutsy Network Manager 0.6.5 and Ndiswrapper fails to connect to hidden AP https://bugs.launchpad.net/bugs/156786 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
