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 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]: <info> [1461938660.4971] manager: wake requested (sleeping: yes enabled: yes) Apr 29 09:04:20 x1 NetworkManager[849]: <info> [1461938660.4971] manager: waking up... Apr 29 09:04:20 x1 NetworkManager[849]: <info> [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]: <info> [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 0000:04:00.0: L1 Enabled - LTR Enabled Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected Apr 29 09:04:20 x1 NetworkManager[849]: <info> [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]: <info> [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]: <info> [1461938661.1095] device (wlp4s0): supplicant interface state: starting -> ready Apr 29 09:04:21 x1 NetworkManager[849]: <info> [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]: <info> [1461938664.1646] device (wlp4s0): supplicant interface state: ready -> inactive Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1678] policy: auto-activating connection 'chiluks-5g 1' Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1688] device (wlp4s0): Activation: starting connection 'chiluks-5g 1' (8c69564c-5b6f-4ab4-8e6e-ee3157160892) Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1690] device (wlp4s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1691] manager: NetworkManager state is now CONNECTING Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1698] device (wlp4s0): state change: prepare -> config (reason 'none') [40 50 0] Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1700] device (wlp4s0): Activation: (wifi) access point 'chiluks-5g 1' has security, but secrets are required. Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1700] device (wlp4s0): state change: config -> need-auth (reason 'none') [50 60 0] Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1741] device (wlp4s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1745] device (wlp4s0): state change: prepare -> config (reason 'none') [40 50 0] Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1747] device (wlp4s0): Activation: (wifi) connection 'chiluks-5g 1' has security, and secrets exist. No new secrets needed. Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1747] Config: added 'ssid' value 'chiluks-5g' Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1749] Config: added 'scan_ssid' value '1' Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1749] Config: added 'key_mgmt' value 'WPA-PSK' Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1749] Config: added 'auth_alg' value 'OPEN' Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1749] Config: added 'psk' value '<omitted>' Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.1858] sup-iface[0x2249d60,wlp4s0]: config: set interface ap_scan to 1 Apr 29 09:04:24 x1 gnome-session[2037]: (nm-applet:2197): nm-applet-CRITICAL **: get_menu_item_for_ap: assertion 'dup_data.hash != NULL' failed Apr 29 09:04:24 x1 gnome-session[2037]: message repeated 6 times: [ (nm-applet:2197): nm-applet-CRITICAL **: get_menu_item_for_ap: assertion 'dup_data.hash != NULL' failed] Apr 29 09:04:24 x1 wpa_supplicant[1102]: wlp4s0: SME: Trying to authenticate with 30:85:a9:e6:8d:ac (SSID='chiluks-5g' freq=5825 MHz) Apr 29 09:04:24 x1 kernel: [180455.536082] wlp4s0: authenticate with 30:85:a9:e6:8d:ac Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2048] device (wlp4s0): supplicant interface state: inactive -> authenticating Apr 29 09:04:24 x1 kernel: [180455.544486] wlp4s0: send auth to 30:85:a9:e6:8d:ac (try 1/3) Apr 29 09:04:24 x1 wpa_supplicant[1102]: wlp4s0: Trying to associate with 30:85:a9:e6:8d:ac (SSID='chiluks-5g' freq=5825 MHz) Apr 29 09:04:24 x1 kernel: [180455.548879] wlp4s0: authenticated Apr 29 09:04:24 x1 wpa_supplicant[1102]: wlp4s0: Associated with 30:85:a9:e6:8d:ac Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2142] device (wlp4s0): supplicant interface state: authenticating -> associating Apr 29 09:04:24 x1 kernel: [180455.551875] wlp4s0: associate with 30:85:a9:e6:8d:ac (try 1/3) Apr 29 09:04:24 x1 kernel: [180455.552890] wlp4s0: RX AssocResp from 30:85:a9:e6:8d:ac (capab=0x11 status=0 aid=2) Apr 29 09:04:24 x1 kernel: [180455.554081] wlp4s0: associated Apr 29 09:04:24 x1 kernel: [180455.554109] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2190] device (wlp4s0): supplicant interface state: associating -> associated Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2293] device (wlp4s0): supplicant interface state: associated -> 4-way handshake Apr 29 09:04:24 x1 wpa_supplicant[1102]: wlp4s0: WPA: Key negotiation completed with 30:85:a9:e6:8d:ac [PTK=CCMP GTK=CCMP] Apr 29 09:04:24 x1 wpa_supplicant[1102]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to 30:85:a9:e6:8d:ac completed [id=0 id_str=] Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2394] device (wlp4s0): supplicant interface state: 4-way handshake -> completed Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2395] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'chiluks-5g'. Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2395] device (wlp4s0): state change: config -> ip-config (reason 'none') [50 70 0] Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2401] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds) Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2413] dhcp4 (wlp4s0): dhclient started with pid 19271 Apr 29 09:04:24 x1 dhclient[19271]: DHCPREQUEST of 192.168.1.197 on wlp4s0 to 255.255.255.255 port 67 (xid=0x5677df51) Apr 29 09:04:24 x1 dhclient[19271]: DHCPACK of 192.168.1.197 from 192.168.1.1 Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2784] address 192.168.1.197 Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2784] plen 24 (255.255.255.0) Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2784] gateway 192.168.1.1 Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2784] server identifier 192.168.1.1 Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2785] lease time 86400 Apr 29 09:04:24 x1 avahi-daemon[783]: Joining mDNS multicast group on interface wlp4s0.IPv4 with address 192.168.1.197. Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2785] hostname 'x1' Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2785] nameserver '192.168.1.1' Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2785] dhcp4 (wlp4s0): state changed unknown -> bound Apr 29 09:04:24 x1 avahi-daemon[783]: New relevant interface wlp4s0.IPv4 for mDNS. Apr 29 09:04:24 x1 avahi-daemon[783]: Registering new address record for 192.168.1.197 on wlp4s0.IPv4. Apr 29 09:04:24 x1 dhclient[19271]: bound to 192.168.1.197 -- renewal in 39558 seconds. Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2862] device (wlp4s0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Apr 29 09:04:24 x1 whoopsie[855]: [09:04:24] Cannot reach: https://daisy.ubuntu.com Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2885] device (wlp4s0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2889] device (wlp4s0): state change: secondaries -> activated (reason 'none') [90 100 0] Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2891] manager: NetworkManager state is now CONNECTED_LOCAL Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2949] manager: NetworkManager state is now CONNECTED_GLOBAL Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2950] policy: set 'chiluks-5g 1' (wlp4s0) as default for IPv4 routing and DNS Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.2951] dns-mgr: Writing DNS information to /sbin/resolvconf Apr 29 09:04:24 x1 dnsmasq[1806]: setting upstream servers from DBus Apr 29 09:04:24 x1 dnsmasq[1806]: using nameserver 192.168.1.1#53 Apr 29 09:04:24 x1 NetworkManager[849]: <info> [1461938664.3023] device (wlp4s0): Activation: successful, device activated. Apr 29 09:04:24 x1 nm-dispatcher: req:2 'up' [wlp4s0]: new request (2 scripts) Apr 29 09:04:24 x1 nm-dispatcher: req:2 'up' [wlp4s0]: start running ordered scripts... Apr 29 09:04:24 x1 gnome-session[2037]: (nm-applet:2197): nm-applet-CRITICAL **: get_menu_item_for_ap: assertion 'dup_data.hash != NULL' failed Apr 29 09:04:24 x1 gnome-session[2037]: message repeated 6 times: [ (nm-applet:2197): nm-applet-CRITICAL **: get_menu_item_for_ap: assertion 'dup_data.hash != NULL' failed] __________________________________________________________________ I will attempt to look at this more thoroughly as I get time, but for now I'll just open the bug so others can fell some solidarity if this is more widespread. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 29 09:49:05 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-25 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp4s0 proto static metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.197 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576747/+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
