network-manager and wifi not working after resume from suspend

Bug #1310595 reported by G.C. Hassink
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After resume from suspend, wifi light stays off but wifi connects.
After resume from suspend second time, wifi does not connect and network -manager says network not activated, activate network does not help. only reboot does.

additional info. I added:

# WORKAROUND: always set the default hibernate mode first (normal mode)
# (not required if you have the patch mentioned by Rohan below (http://askubuntu.com/a/344879/169))
HIBERNATE_MODE=platform

# Always use hibernate instead of suspend, but with "suspend to both"
if [ "$METHOD" = "suspend" ]; then
  METHOD=hibernate
  HIBERNATE_MODE=suspend
fi

# Make sure to use the kernel's method, in case uswsusp is installed etc.
SLEEP_MODULE=kernel

to /etc/pm/config.d/00-use-suspend-hybrid
to be able to suspend to disk.

Without this file wifi connects after resuspend but as said without wifi light on. This was not the case for Ubuntu 13.10

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CRDA:
 country PE:
  (2402 - 2482 @ 40), (N/A, 20)
  (5735 - 5835 @ 40), (N/A, 30)
CurrentDesktop: Unity
Date: Mon Apr 21 14:21:41 2014
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-10-25 (177 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IpRoute:
 default via 192.168.1.254 dev wlan0 proto static
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.33 metric 9
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to trusty on 2014-04-18 (2 days ago)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 00:22:66:97:02:8D bluetooth disconnected /org/freedesktop/NetworkManager/Devices/3
 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1
 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.8 connected enabled enabled enabled enabled enabled

Revision history for this message
G.C. Hassink (gchassink) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Sydney Dykstra (sydneyjd) wrote :

I am having this problem on ubuntu 14.04 32bit,except that it does connect,but its slow.The light doesnt come on,and the internet is not fast till I reboot. I am using a Netgear WNA WNA1100.

Revision history for this message
Karim Mesallam (karim-mesallam) wrote :

I was having this same problem on Ubuntu 14.04 and after a couple of days of trying to fix it, I found a file inside /etc/pm/sleep.d/ which is called 99dw1704. This file handles disabling and enabling the wl module on hibernate and suspend. All I had to do to fix it is to run: sudo chmod -x /etc/pm/sleep.d/99dw1704

Revision history for this message
Hans Deragon (deragon) wrote :

At a high level, I have the same problem: Network Mnager does not work anymore after resume, about half the time.

My work around is to run in a terminal: sudo restart network-manager

As a side effect, nm-applet sometimes crashes when I do that. But it works.

At a lower level, I am not sure if my problem is the same as the original poster; I am not familiar with Network Manager so I have not yet bothered to dig deep into the logs to figure out what is going one. I could post the logs if requested.

Revision history for this message
Hans Deragon (deragon) wrote :

@Sydney Dykstra (sydneyjd) , I do not believe you are having the same problem. You should hunt for another ticket or create a new one.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.