[Desktop-packages] [Bug 1857655] Re: gdkselection-wayland.c:275: error reading selection buffer

2020-09-30 Thread Christian Kujau
** Bug watch added: Red Hat Bugzilla #1413858
   https://bugzilla.redhat.com/show_bug.cgi?id=1413858

** Also affects: wayland-protocols (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1413858
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1857655

Title:
  gdkselection-wayland.c:275: error reading selection buffer

Status in nautilus package in Ubuntu:
  Expired
Status in wayland-protocols package in Fedora:
  Unknown

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu1
  3) No error.
  4) Error in Logs app.

  6:41:01 PM nautilus: ../../../../../gdk/wayland/gdkselection-
  wayland.c:275: error reading selection buffer: Operation was cancelled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857655/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys

2018-02-25 Thread Christian Kujau
** Changed in: gnome-keyring (Ubuntu)
   Status: Triaged => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/771272

Title:
  gnome-keyring doesn't support ecdsa or ed25519 keys

Status in GNOME Keyring:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Debian:
  Fix Released

Bug description:
  Binary package hint: gnome-keyring

  I'm not sure I have described it correctly in the summary, but this is what 
happens:
  I run ssh-add in a new terminal and enter my passphrase, which is the same 
for my DSA and ECDSA key: the DSA identity is added, but the ECDSA gets the 
"Error reading response length from authentication socket. Could not add 
identity: /home/claudio/.ssh/id_ecdsa" error.
  I run ssh-agent, copy and paste the output in the terminal and re-run 
ssh-add. Both identities are correctly added:
  
  claudio@Chuck:~$ ssh-add 
  Enter passphrase for /home/claudio/.ssh/id_dsa: 
  Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa)
  Error reading response length from authentication socket.
  Could not add identity: /home/claudio/.ssh/id_ecdsa
  claudio@Chuck:~$ ssh-agent 
  SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export SSH_AUTH_SOCK;
  SSH_AGENT_PID=3917; export SSH_AGENT_PID;
  echo Agent pid 3917;
  claudio@Chuck:~$ SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export 
SSH_AUTH_SOCK;
  claudio@Chuck:~$ SSH_AGENT_PID=3917; export SSH_AGENT_PID;
  claudio@Chuck:~$ echo Agent pid 3917;
  Agent pid 3917
  claudio@Chuck:~$ ssh-add 
  Enter passphrase for /home/claudio/.ssh/id_dsa: 
  Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa)
  Identity added: /home/claudio/.ssh/id_ecdsa (/home/claudio/.ssh/id_ecdsa)
  
  Here is the content of my ~/.ssh/

  claudio@Chuck:~$ ls -l .ssh
  total 32
  -rw-r--r-- 1 claudio claudio  726 2011-04-15 23:34 config
  -r 1 claudio claudio  751 2011-04-05 10:35 id_dsa
  -rw-r--r-- 1 claudio claudio  603 2011-04-05 10:34 id_dsa.pub
  -r 1 claudio claudio  444 2011-04-05 10:29 id_ecdsa
  -rw-r--r-- 1 claudio claudio  267 2011-04-05 10:23 id_ecdsa.pub
  -rw--- 1 claudio claudio 6402 2011-04-19 18:04 known_hosts
  -rw-r--r-- 1 claudio claudio 2760 2011-04-06 17:05 known_hosts.old

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-keyring 2.92.92.is.2.32.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue Apr 26 16:27:02 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to natty on 2011-04-03 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2017-11-04 Thread Christian Kujau
*** This bug is a duplicate of bug 578431 ***
https://bugs.launchpad.net/bugs/578431

** This bug has been marked a duplicate of bug 578431
   wpa_supplicant spams syslog

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in wpa package in Ubuntu:
  Invalid

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2017-10-30 Thread Christian Kujau
Launchpad really needs something similar to RESOLVED/DUPLICATE, as I had
to crawl through the whole report to find out that this is considered a
duplicate of 578431.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

Status in wpa package in Ubuntu:
  Invalid

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys

2015-10-10 Thread Christian Kujau
** Summary changed:

- ssh-add does not handle ECDSA keys until ssh-agent exports are manually 
launched
+ gnome-keyring doesn't support ecdsa or ed25519 keys

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/771272

Title:
  gnome-keyring doesn't support ecdsa or ed25519 keys

Status in GNOME Keyring:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in gnome-keyring package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-keyring

  I'm not sure I have described it correctly in the summary, but this is what 
happens:
  I run ssh-add in a new terminal and enter my passphrase, which is the same 
for my DSA and ECDSA key: the DSA identity is added, but the ECDSA gets the 
"Error reading response length from authentication socket. Could not add 
identity: /home/claudio/.ssh/id_ecdsa" error.
  I run ssh-agent, copy and paste the output in the terminal and re-run 
ssh-add. Both identities are correctly added:
  
  claudio@Chuck:~$ ssh-add 
  Enter passphrase for /home/claudio/.ssh/id_dsa: 
  Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa)
  Error reading response length from authentication socket.
  Could not add identity: /home/claudio/.ssh/id_ecdsa
  claudio@Chuck:~$ ssh-agent 
  SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export SSH_AUTH_SOCK;
  SSH_AGENT_PID=3917; export SSH_AGENT_PID;
  echo Agent pid 3917;
  claudio@Chuck:~$ SSH_AUTH_SOCK=/tmp/ssh-szGWMUbE3916/agent.3916; export 
SSH_AUTH_SOCK;
  claudio@Chuck:~$ SSH_AGENT_PID=3917; export SSH_AGENT_PID;
  claudio@Chuck:~$ echo Agent pid 3917;
  Agent pid 3917
  claudio@Chuck:~$ ssh-add 
  Enter passphrase for /home/claudio/.ssh/id_dsa: 
  Identity added: /home/claudio/.ssh/id_dsa (/home/claudio/.ssh/id_dsa)
  Identity added: /home/claudio/.ssh/id_ecdsa (/home/claudio/.ssh/id_ecdsa)
  
  Here is the content of my ~/.ssh/

  claudio@Chuck:~$ ls -l .ssh
  total 32
  -rw-r--r-- 1 claudio claudio  726 2011-04-15 23:34 config
  -r 1 claudio claudio  751 2011-04-05 10:35 id_dsa
  -rw-r--r-- 1 claudio claudio  603 2011-04-05 10:34 id_dsa.pub
  -r 1 claudio claudio  444 2011-04-05 10:29 id_ecdsa
  -rw-r--r-- 1 claudio claudio  267 2011-04-05 10:23 id_ecdsa.pub
  -rw--- 1 claudio claudio 6402 2011-04-19 18:04 known_hosts
  -rw-r--r-- 1 claudio claudio 2760 2011-04-06 17:05 known_hosts.old

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-keyring 2.92.92.is.2.32.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue Apr 26 16:27:02 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to natty on 2011-04-03 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1067301] Re: ssh-add: Error reading response length from authentication socket.

2015-01-11 Thread Christian Kujau
** Bug watch added: Debian Bug tracker #738660
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738660

** Also affects: gnome-keyring (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738660
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1067301

Title:
  ssh-add: Error reading response length from authentication socket.

Status in GNOME keyring services:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Debian:
  Unknown

Bug description:
  ssh-add seems not to work with the confirmation (-c) option.  Trying
  to require that identities be subject to confirmation when used brings
  up the error "Error reading response length from authentication
  socket. "

   $ ssh-add -c /home/user/.ssh/key_rsa 
   Enter passphrase for /home/user/.ssh/key_rsa: 
   Error reading response length from authentication socket.
   Could not add identity: /home/user/.ssh/key_rsa

  Addding keys not subject to confirmation when used works as normal:

   $ ssh-add  /home/user/.ssh/key_rsa 
   Enter passphrase for /home/user/.ssh/key_rsa: 
   Identity added: /home/user/.ssh/key_rsa (/home/user/.ssh/key_rsa)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: openssh-client 1:6.0p1-3ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Tue Oct 16 13:55:08 2012
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64+mac 
(20121015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/1067301/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes

2014-11-14 Thread Christian Kujau
Same here, every 2 minutes with wpa_supplicant v2.3:

$ sudo grep wpa_supplicant /var/log/messages | grep -v WPA | tail -3
Nov 14 11:24:32 acorn wpa_supplicant[942]: nl80211: send_and_recv->nl_recvmsgs 
failed: -33
Nov 14 11:26:32 acorn wpa_supplicant[942]: nl80211: send_and_recv->nl_recvmsgs 
failed: -33
Nov 14 11:28:32 acorn wpa_supplicant[942]: nl80211: send_and_recv->nl_recvmsgs 
failed: -33

No connectivity issues though, rekeying happens just fine every 10min:

$ sudo grep wpa_supplicant /var/log/messages | grep WPA | tail -3
Nov 14 11:07:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed 
with  [GTK=CCMP]
Nov 14 11:17:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed 
with  [GTK=CCMP]
Nov 14 11:27:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed 
with  [GTK=CCMP]

Wifi chip:
04:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp