touch-packages team mailing list archive

Thread
Date
[Bug 294190] Re: spews logs with "supplicant connection state change"

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Bryan Quigley <bryan.quigley@xxxxxxxxxxxxx>
Date: Fri, 22 Jan 2016 20:02:51 -0000
Reply-to: Bug 294190 <294190@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
This bug was marked Incomplete some time ago and was supposed to
autoclose after 90 days.  I'm going to close it manually due to no
activity (and likely the issue has gone away/been fixed).

** Changed in: network-manager (Ubuntu)
       Status: Incomplete => Invalid

** Changed in: network-manager
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/294190

Title:
  spews logs with "supplicant connection state change"

Status in NetworkManager:
  Invalid
Status in wpa_supplicant:
  Won't Fix
Status in network-manager package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: network-manager

  NetworkManager completely clogs up all the system logs with messages
  like this:

  Nov  5 01:36:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 7 -> 0
  Nov  5 01:36:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 0 -> 2
  Nov  5 01:36:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 2 -> 3
  Nov  5 01:36:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 3 -> 4
  Nov  5 01:36:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 4 -> 5
  Nov  5 01:36:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 5 -> 6
  Nov  5 01:36:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 6 -> 7
  Nov  5 01:38:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 7 -> 0
  Nov  5 01:38:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 0 -> 2
  Nov  5 01:38:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 2 -> 3
  Nov  5 01:38:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 3 -> 4
  Nov  5 01:38:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 4 -> 5
  Nov  5 01:38:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 5 -> 6
  Nov  5 01:38:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 6 -> 7
  Nov  5 01:40:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 7 -> 0
  Nov  5 01:40:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 0 -> 2
  Nov  5 01:40:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 2 -> 3
  Nov  5 01:40:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 3 -> 4
  Nov  5 01:40:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 4 -> 5
  Nov  5 01:40:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 5 -> 6
  Nov  5 01:40:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 6 -> 7
  Nov  5 01:42:35 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 7 -> 0
  Nov  5 01:42:35 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 0 -> 2
  Nov  5 01:42:36 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 2 -> 3
  Nov  5 01:42:36 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 3 -> 4
  Nov  5 01:42:36 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 4 -> 5
  Nov  5 01:42:36 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 5 -> 6
  Nov  5 01:42:36 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 6 -> 7
  Nov  5 01:44:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 7 -> 0
  Nov  5 01:44:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 0 -> 2
  Nov  5 01:44:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 2 -> 3
  Nov  5 01:44:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 3 -> 4
  Nov  5 01:44:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 4 -> 5
  Nov  5 01:44:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 5 -> 6
  Nov  5 01:44:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 6 -> 7
  Nov  5 01:46:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 7 -> 0
  Nov  5 01:46:32 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 0 -> 2
  Nov  5 01:46:33 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 2 -> 3
  Nov  5 01:46:34 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 3 -> 4
  Nov  5 01:46:34 inspiron NetworkManager: <info>  (eth1): supplicant connection state change: 4 -> 5

  If this stuff really needs to be logged for some reason, can't it be
  directed to its own file?  It makes the logs really difficult to read
  and wastes disk space.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/294190/+subscriptions