[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Please try network-manager-1.2.6 from xenial-proposed, if you have 16.04. For me it seems to fix this bug. But when you will test don't forget to turn off all self-made scripts to see if it really does the job. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Seems it works for my Lenovo x230t. Thanks for your effort! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: Triaged Status in network-manager package in Ubuntu: Confirmed Bug description: HOW TO REPRODUCE: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 RESULT: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. WORKAROUND: (http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade) SYSTEM INFO: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
@deragon Yes, you are right, there is related bug, see bug #1589401. But I'm pretty sure this have one origin and it is wifi driver, especially for intel cards. If you look at the bottom of the discussion on the mentioned bug, you'll find that problem remains even after change to another network manager, so it is deeper than it may look. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
@jasauders Problem is that bug is present not only for suspend/resume scenario, but also for wifi on/off. And for me it even drop connection sometimes and can't reconnect without wifi restart. It's a problem with wifi drivers and devs not seems to care about it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Centrino Advanced-N 6205 here too. I have different issues from time to time, I'd rather say I have every one described on this page. But they happen without some strict manner, the only thing for sure is that after every suspend I have to restart nm-applet to bring it back to normal work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
yeah, canonical, is anyone there?! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04
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 Ubuntu Touch seeded 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]:
[Touch-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04
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 Ubuntu Touch seeded 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):
[Touch-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04
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 Ubuntu Touch seeded 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]:
[Touch-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04
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 Ubuntu Touch seeded 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'
[Touch-packages] [Bug 1430103] [NEW] package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured
*** This bug is a duplicate of bug 1424347 *** https://bugs.launchpad.net/bugs/1424347 Public bug reported: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured ProblemType: Package DistroRelease: Ubuntu 14.04 Package: language-pack-gnome-en-base 1:14.04+20150219 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.7 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Mon Mar 9 21:26:02 2015 DuplicateSignature: package:language-pack-gnome-en-base:1:14.04+20150219:package language-pack-gnome-en-base is already installed and configured ErrorMessage: package language-pack-gnome-en-base is already installed and configured InstallationDate: Installed on 2015-02-08 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: language-pack-gnome-en-base Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: language-pack-gnome-en-base (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en- base in Ubuntu. https://bugs.launchpad.net/bugs/1430103 Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured Status in language-pack-gnome-en-base package in Ubuntu: New Bug description: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured ProblemType: Package DistroRelease: Ubuntu 14.04 Package: language-pack-gnome-en-base 1:14.04+20150219 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.7 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Mon Mar 9 21:26:02 2015 DuplicateSignature: package:language-pack-gnome-en-base:1:14.04+20150219:package language-pack-gnome-en-base is already installed and configured ErrorMessage: package language-pack-gnome-en-base is already installed and configured InstallationDate: Installed on 2015-02-08 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: language-pack-gnome-en-base Title: package language-pack-gnome-en-base 1:14.04+20150219 failed to install/upgrade: package language-pack-gnome-en-base is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en-base/+bug/1430103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp