I'm experiencing this, too. At least on my WPA EAP-TLS network.
Check it : May 16 14:38:56 portable-alex NetworkManager: <info> (wlan0): supplicant connection state: completed -> disconnected May 16 14:38:56 portable-alex NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning May 16 14:38:56 portable-alex NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected May 16 14:39:00 portable-alex NetworkManager: <debug> [1242477540.003783] periodic_update(): Roamed from BSSID 00:12:A9:0A:78:F5 (ssid) to (none) ((none)) May 16 14:39:02 portable-alex NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associating May 16 14:39:03 portable-alex NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated May 16 14:39:06 portable-alex NetworkManager: <debug> [1242477546.003040] periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:A9:0A:78:F5 (ssid) May 16 14:39:12 portable-alex NetworkManager: <info> (wlan0): device state change: 8 -> 3 May 16 14:39:12 portable-alex NetworkManager: <info> (wlan0): deactivating device (reason: 11). It looks like it makes Network Manager and/or underlying WPA Supplicant loosing the association with the access point. -- network-manager roams to (none) ((none)) https://bugs.launchpad.net/bugs/291760 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
