New to wpa_supplicant and wpa_cli and am using systemd-resolved as network manager. I have everything working reasonably well, but struggled with one thing. I get this error flooding the journal log: Jul 01 13:26:10 pi4 wpa_supplicant[420]: wlan0: Failed to initiate sched scan Jul 01 13:26:19 pi4 wpa_supplicant[420]: wlan0: Failed to initiate sched scan Jul 01 13:26:28 pi4 wpa_supplicant[420]: wlan0: Failed to initiate sched scan This occurs when there is a known ssid in the config, the ssid is enabled by wpa_cli, but this ssid is not visible and the wlan is not connected to any other ssid. If I disable the network: 'wpa_cli disable network 0', it stops spamming the log. If It stays enabled yet I connect to another ssid, it does not spam the log. It is only when it is not connected and there is an ssid in the config that it cannot 'see'. It appears that when wpa_supplicant is complaining that it 'Failed to initiate sched scan' it will immediately connect to that known network when it reappears. As long as the ssid is not available, and is in the list (in /etc/wpa_supplicant.conf) and 'enabled' by wpa_cli the log gets spammed with this. It seems a bit strange that this would be an unexpected situation: that wpa_supplicant may not be connected yet have an ssid listed that may not be available. I am running this on an RPi which is running RPiOS with systemd and have tried this with wpa_supplicant.service (dbus version edited to specify wlan0 so that it can save the configs) and with wpa_supplicant@wlan0 (without dbus). Any help appreciated.
