This WorkAround also works for me :
- from the gnome network manager, launch the connection
- find the wpa PID by a 'ps -ef | grep wpa_supplicant'
- do a 'sudo renice 19 wpa_pid' , replace wpa_pid by the wpa_supplicant PID
Now i understand why sometimes, it can connect without this workaround, it's when i launch the connection when the PC is very busy.
This WorkAround also works for me :
- from the gnome network manager, launch the connection
- find the wpa PID by a 'ps -ef | grep wpa_supplicant'
- do a 'sudo renice 19 wpa_pid' , replace wpa_pid by the wpa_supplicant PID
Now i understand why sometimes, it can connect without this workaround, it's when i launch the connection when the PC is very busy.
--
Chri