desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #145940
[Bug 1422143] Re: No wifi connection after suspend with systemd
Hello Fran, or anyone else affected,
Accepted wpa into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/wpa/2.4-0ubuntu3.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: wpa (Ubuntu Wily)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
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
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
References