Network Manager needs restarting from sleep
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Each time my laptop is suspended and resumed, Network Manager seems unable to bring up Wifi.
Calling...
sudo service network-manager restart
...resolves the problem.
I therefore placed the attached file at...
/lib/systemd/
...which provides a workaround for the problem. However, there must be some kind of underlying bug in network-manager which requires it to be restarted after every suspend/resume cycle.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.
ProcVersionSign
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: LXDE
Date: Tue Mar 28 10:21:35 2017
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
default via 192.168.1.1 dev wlp1s0 proto static metric 600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.203 metric 600
JournalErrors:
Error: command ['journalctl', '-b', '--priority=
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
docker0 bridge connected /org/freedeskto
wlp1s0 wifi connected /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.2.6 connected started full enabled enabled enabled enabled enabled
Changed in network-manager (Ubuntu): | |
importance: | Undecided → Medium |
Status changed to 'Confirmed' because the bug affects multiple users.