Description of problem: wpa_supplicant fails to connect to network since upgrade to fedora 34 May 01 18:44:13 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:14 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:15 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:16 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:17 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:18 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:19 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:20 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:21 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:22 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:23 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:24 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:25 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:26 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:27 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:28 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:29 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:30 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:31 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:32 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:33 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:34 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:35 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:36 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:37 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 May 01 18:44:38 reflection wpa_supplicant[249961]: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. set up 2Ghz/5Ghz AP 2. install centrino 6200 intel wifi card 3. configure network manager to connect to AP 4. reboot Actual results: wifi remains unconnected, wpa_supplicant repeatedly outputs: wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1 Expected results: connect to network Additional info: this is using iwl6000-firmware with the following lspci entry: 02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) sometimes a connection will be made eventually. the router has both 2.4Ghz/5Ghz mode. If I set up a 2.4Ghz only hotspot on my phone then it works fine.
After some further investigation I found that the problem is likely not wpa_supplicant itself, if I invoke wpa_supplicant manually with an appropriate config it will connect immediately: [root@reflection wpa_supplicant]# wpa_supplicant -Dwext -iwlp2s0 -c wpa_supplicant_sky.conf Successfully initialized wpa_supplicant ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCSIWENCODEEXT]: Invalid argument wlp2s0: Trying to associate with [omitted] (SSID='[omitted]' freq=5180 MHz) Failed to add supported operating classes IE wlp2s0: Associated with [omitted] wlp2s0: WPA: Key negotiation completed with [omitted] [PTK=CCMP GTK=CCMP] wlp2s0: CTRL-EVENT-CONNECTED - Connection to [omitted] completed [id=0 id_str=] so maybe the problem is network manager?
I have the same problem. What is in your wpa_supplicant_sky.conf file?
Nice to know it's not just me, here's what I have: # cat etc/wpa_supplicant/wpa_supplicant_sky.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ scan_ssid=1 ssid="MYSSIDHERE" psk="MYWIFIPASSHERE" }
Same Problem here. Controller is: 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
Centrino Advanced-N 6200 here. Problem first started when I updated Fedora 33 right before upgrading to 34, so I don't think 34 is the only release affected.
Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) here on F34 NO trouble connecting, to different APs and neither frequency. However I am getting the same error message every 10 seconds - clockwork consistency.
same here. Version 2.9 of wpa_supplicant still worked like a breeze. F35
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.