[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-07-07 Thread Dave Chiluk
Not a duplicate of 1585863, as 
$ sudo wpa_cli scan
does not recover nm-applet functionality.  There seem to be a number of similar 
but different issues related to wifi. 

** This bug is no longer a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Ap

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-07-06 Thread Martin Wimpress
*** This bug is a duplicate of bug 1585863 ***
https://bugs.launchpad.net/bugs/1585863

** This bug has been marked a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): st

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-07-01 Thread monte
Here is my syslog after resume. Sorry for so long time without reply. 
And there are errors in log related to bluez service, as it don't work properly 
after suspend either, so I need to use script to restart it automatically on 
resume.

** Attachment added: "syslog debug"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576747/+attachment/4693456/+files/syslog_debug

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-06-13 Thread Dave Chiluk
@monte

Alright thanks for the test. Can you please add --log-level=debug to 
/lib/systemd/system/NetworkManager.service at the end of the ExecStart= line.  
So it looks like this
ExecStart=/usr/sbin/NetworkManager --no-daemon --log-level=debug
Then
- restart your machine.
- suspend the machine.
- resume the machine.  Verifying that you hit the issue.
- Then upload your syslog as I did above.

Thank you,
Dave

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManag

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-06-13 Thread monte
Ok, thanks for a hint. Found Intel Management Engine Firmware 8.1 for my
lenovo x230t, installed it on Windows 7, rebooted into Ubuntu, but bug
is still present, same as it was before.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-06-13 Thread Dave Chiluk
There is a firmware component for IMEI.  If I'm not mistaken the IMEI
firmware is what is responsible for vpro / AMT functionality.  According
to this FAQ https://software.intel.com/en-us/articles/intel-vpro-
technology-faq, it is capable of controlling a wireless card even while
in sleep states.  This could be putting the card in an unexpected state
while in suspend/sleep.

The update I installed was not simply a windows driver update, but
actually a firmware flash presumably for the formentioned vpro/amt
functionality.

That being said if your machines are not vpro/amt capable then that's
clearly not your issue, but until I hit that issue again it does seem to
be what resolved my issue.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-06-13 Thread Nick Kleeman
I think the IMEI firmware is a fluke, plus that is not really a solution
for everyone as it is just a windows driver, and not everyone is dual
booting. It's "Intel Management Engine Interface" only reference I can
find to "IMEI" that makes sense.

On a side note, I just deleted my windows partition about a week ago and
was up to date of the time, also on Dell's website the IMEI is from
February 2016.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]: 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-06-13 Thread monte
IMEI firmware update for wifi card? Do they even have IMEI, never heard
of it.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-06-13 Thread Dave Chiluk
So I don't seem to be able to reproduce this any more.  I did recently
boot windows on my laptop, and then ran updates.  I no longer seem to be
able to reproduce this issue.

One of the important updates was an update to the IMEI firmware on my
machine.  Can someone else on this bug please upgrade your IMEI firmware
*(which likely needs to be performed via windows), and then attempt to
reproduce this bug.  I'd like confirmation that the IMEI firmware update
did indeed resolve this issue.

Thanks

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.16

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-06-02 Thread Dave Chiluk
@cyphermox

Here's the debug output we worked on today.  I removed most everything
from before I suspended the machine.  Everything remaining is either
from the suspend or the resume.

The output was achieved by adding --log-level=debug to
/lib/systemd/system/NetworkManager.service at the ExecStart= line, and
then restarting.

** Attachment added: "syslog debug output."
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576747/+attachment/4675543/+files/syslog

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-a

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-06-02 Thread Dave Chiluk
I went tested the patches for 1585863, but still saw the issue.

** This bug is no longer a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> pr

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-06-02 Thread Dave Chiluk
*** This bug is a duplicate of bug 1585863 ***
https://bugs.launchpad.net/bugs/1585863

This appears to be getting some progress via 1585863, so I'm marking it
as a dupe, even though this one is older.

** This bug has been marked a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c695

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-26 Thread monte
Have this bug on fresh install on Lenovo x230t, Intel 6205 card. Have to
restart nm-applet after every suspend. It seems that restart of network-
manager service produces same bug to applet. I mean doing "sudo service
network-manager restart" brokes nm-applet, so I need to restart it
manually.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-20 Thread maarten
Happening on an Asus N53 laptop. (AR9285 Wireless network adapter).
Problem is annoying to consider rolling back to previous version. Not an
easy job. Didn't have to do that in many years of upgrading.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-20 Thread Dave Chiluk
I just tried 1.2.0-0ubuntu0.16.04.2, shutdown, started up, suspended
resumed, and still see this issue.

I'm sorry, I haven't had more time to debug this myself.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-19 Thread Sebastien Bacher
can you try to xenial-proposed update and see if it improves things for
you?

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.16

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-18 Thread Dave Chiluk
@aeaeaeaeaeae, virbr0 is owned/created by libvirt as the default network
for kvm.  This issue very likely unrelated.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 29 09:04:24 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-18 Thread Aeaeaeaeaeae
is it possible that there is a link to the mysterious "vribr0"?
...it occurs both in the initial bug desription here, and on my laptop too (I 
did not configure virbr0 anywhere, but its there since the installation of 
16.04, when the wifi problem started)

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 N

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-11 Thread Dave Chiluk
Well under further review.  Moving wifi zones does not seem to be
necessary, but sleeping for some extended time may be.

I can also confirm that killing and restarting nm-applet is another
less-hammerlike workaround.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690]

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-11 Thread Alberto Salvia Novella
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1691] 

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-06 Thread Dave Chiluk
So it looks as though I'm able to reproduce this by 
1. Connecting to wifi access point
2. Suspend
3. Move out of range, but in range of another saved access point.
4. Resume.

My computer automatically connected to the new access point, but does
not show any information to that effect.

I'm not sure if the new saved access point is required, but either way
you will no longer be able to manage wireless networks through the
applet.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-06 Thread Dave Chiluk
It's possible.  I'll mark this as a dupe once we know more.

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1691] manager: 
Net

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-05-03 Thread Martin
Could be the same like this? https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1516153

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  Apr 29 09:04:24 x1 NetworkManage

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

2016-04-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> prepare (reason 'none') [3