I'm not Anne and I don't fully remember this "bug". I believe it was about
Linux looking for new WiFi routers to connect to every 2 minutes and
issuing a message when one was not found. This given there should be an
option within Ubuntu Network Manager (or whomever) to not message every 2
minutes when a new WiFi connection is not found.

On Sat, Apr 18, 2015 at 10:21 AM, Neal McBurnett <email address hidden>
wrote:

> Thank you Anne for describing what looks like one way to fix this for
> all connections, rather than the easy fix in #24 which only addresses
> one SSID.
>
> But I worry that making wpa_supplicant more quiet will hide messages
> that are important - what else would be suppressed?
>
> So I suspect that the bug should be fixed somewhere else, since it seems
> clear to me that default installs with popular wifi cards should not
> spam syslog, and this does seem to be related to only some forms of
> Intel wifi cards - mostly Centrino I guess.
>
> So what is printing this out, which developer explained the workaround
> (sometime after 2009?), and how do we clean up our syslogs?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1323089
>
> Title:
>   wpa_supplicant writes to syslog every 2 minutes
>
> Status in wpa package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Ubuntu 14.04 LTS
>   wpasupplicant 2.1-0ubuntu1
>
>   wpa_supplicant is writing to syslog every couple of minutes. Example
>   output:
>
>   May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>   May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0:
> CTRL-EVENT-SCAN-STARTED
>   May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [
> wlan0: CTRL-EVENT-SCAN-STARTED ]
>   May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
>
>   The message seems harmless as far as the network is concerned, meaning
>   there is no problem with the wifi connection. But it's spamming the
>   syslog, making it very difficult to find any other thing there, and
>   it's generating constant writes to disk, and an unnecessarily large
>   syslog file.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+subscriptions
>