Says fix released for xenial. What was it actually released in? wpa_supplicant? I still have the problem intermittently.
May 16 22:58:18 bryan-Latitude-E6410 kernel: iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1 May 16 22:58:19 bryan-Latitude-E6410 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready May 16 22:58:19 bryan-Latitude-E6410 NetworkManager[690]: <info> [1463453899.0483] device (eno1): state change: unmanaged -> unavailable (reason 'managed') [1 May 16 22:58:19 bryan-Latitude-E6410 kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready May 16 22:58:19 bryan-Latitude-E6410 NetworkManager[690]: <info> [1463453899.2606] manager: NetworkManager state is now DISCONNECTED May 16 22:58:19 bryan-Latitude-E6410 kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready May 16 22:58:19 bryan-Latitude-E6410 wpa_supplicant[858]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none May 16 22:58:19 bryan-Latitude-E6410 wpa_supplicant[858]: dbus: Failed to construct signal May 16 22:58:19 bryan-Latitude-E6410 NetworkManager[690]: <info> [1463453899.3049] device (wlp3s0): supplicant interface state: starting -> ready May 16 22:58:19 bryan-Latitude-E6410 NetworkManager[690]: <info> [1463453899.3050] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplic May 16 22:58:19 bryan-Latitude-E6410 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready May 16 22:58:20 bryan-Latitude-E6410 acpid[617]: client connected from 8954[0:0] May 16 22:58:20 bryan-Latitude-E6410 acpid[617]: 1 client rule loaded May 16 22:58:20 bryan-Latitude-E6410 kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1 sudo service network-manager restart seems to fix the problem as suggested above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Confirmed Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Fix Committed Status in wpa source package in Xenial: Fix Released Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. SRU INFORMATION =============== In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridge unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- 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/hundredpapercuts/+bug/1422143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
