No wifi after suspend

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Same problem here with 14.04 and ralink rt73 chipset. Worked perfectly with 13.10

Not related with SUSPEND_MODULES="rt73usb" in /etc/pm/config.d/load (already done and doesn't resolve).

sudo rfkill list
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

There are 24 people affected and many duplicates :

    Bug #1290055
    Bug #1293928
    Bug #1294576
    Bug #1295285
    Bug #1309769

And nobody is assigned to ??

Not a isolated problem :

http://ubuntuforums.org/showthread.php?t=2218043
http://ubuntuforums.org/showthread.php?t=2218445

kernel 3.14-1 from http://kernel.ubuntu.com/~kernel-ppa/mainline does'nt resolve the problem

This is precisely why this bug has been around for at least 3 years. Not only is splintered into countless duplicates under multiple problems each developer points at the other developer and says "oh, its his fault."

If it worked with 3.11 kernel, and don't with 3.13 and 3.14, I think it wouldn't be sooooo chalenging to figure out what the problem is.

Maybe it's not kernel related, cause actualy with 3.11 on 14.04, the wifi doesn't reconnect after suspend either...

How this could be solved some day if no Ubuntu dev team member read it ?? Nobody cares ?

Lol so true. Maybe we should call Ubuntu support...oh wait a minute.

To be honest, my fix was to get rid of network manager and use wicd
instead...though some dist-upgrades put network-manager back on and force
me to purge again.

Since I submitted this bug I'll make sure and clarify...I have had Ubuntu
on this MacBook since 12.04 and had no issue with Wifi. It always
reconnected after sleeping. I have heard from many people that they were
not as lucky, and wifi would NOT reconnect after sleeping with previous
releases. Replacing NM with wicd is a very common approach/workaround due
to this fact. My guess is that devs are so inundated with these bugs that
they've given up on it.

That said, this issue only presented itself when I first went to 14.04 and
not earlier. Each time NM is re-installed on my MBP I run into the same
issue. Wicd is my savior.

On Tue, Apr 22, 2014 at 10:42 AM, nicolas kleinklaus <email address hidden>wrote:

> How this could be solved some day if no Ubuntu dev team member read it
> ?? Nobody cares ?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1290055).
> https://bugs.launchpad.net/bugs/1286552
>
> Title:
> No wifi after suspend
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> After suspending ubuntu the wifi doesn't work. The solution given here
> (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re-
> connecting-after-suspend) worked for me but when I have updated my
> Ubuntu now it won't work. I have tried to test mainline kernel but it
> won't to boot with it.
>
> To reproduce the bug : just suspend the computer and then power it.
> There's no wifi network until you restart the computer.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: ubuntu-release-upgrader-core 1:0.205.4
> ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
> Uname: Linux 3.11.0-15-generic i686
> ApportVersion: 2.12.5-0ubuntu2.2
> Architecture: i386
> CrashDB: ubuntu
> Date: Sat Mar 1 15:20:39 2014
> InstallationDate: Installed on 2013-12-30 (61 days ago)
> InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386
> (20131017)
> MarkForUpload: True
> PackageArchitecture: all
> SourcePackage: ubuntu-release-upgrader
> Symptom: dist-upgrade
> UpgradeStatus: No upgrade log present (probably fresh install)
> ---
> ApportVersion: 2.12.5-0ubuntu2.2
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: meradi 1503 F.... pulseaudio
> DistroRelease: Ubuntu 13.10
> HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf
> InstallationDate: Installed on 2013-12-30 (61 days ago)
> InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386
> (20131017)
> MachineType: Hewlett-Packard HP Compaq 6830s
> MarkForUpload: True
> Package: linux (not installed)
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic
> root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
> RelatedPackageVersions:
> linux-restricted-modules-3.11.0-15-gen...

So the solution is to not use the default programs that Ubuntu considered it's default? Maybe we should switch to another distro or tell people to go back to Windows. Windows would at least have a dev or cs rep tell you something not just ignore you and pretend they don't see it.

FYI I've seen this bug since 11.04

I'm not complaining, BTW. Just doing my part in reporting bugs. I've been
using amazing and free software from Canonical for years now and feel that
reporting bugs is the least I can do. *Least*.

I'm sure Ubuntu product managers have a reason for packaging NM as a
default, and for me it worked for a long time out of the box. Since I'm
not a firmware developer I'm not going to spend the time I need to tweak NM
when wicd works well, though. I could, which is exactly WHY I use Ubuntu
and Linux in general, but I also have the freedom through Ubuntu and Linux
to just install wicd instead, which is what I did and most users seem to
do.

FWIW, I don't know that they're ignoring it. If it's actually a Network
Manager issue then it's actually the NM developer's code and much easier
for them to fix. When Canonical devs are getting paid either nothing or
very little I understand they have to prioritize their work efficiently.
With an easy fix coming by way of using wicd it just doesn't make a ton of
sense for them all to spend time sussing out a weird bug in a package that
isn't even theirs.

I hear ya, just feel like a sleight on Canonical is misplaced. I love
Ubuntu and as long as they pump out a great experience for my needs I will
evangelize for them all day. It's the other least I can do.

On Tue, Apr 22, 2014 at 11:07 AM, justin parker
<email address hidden>wrote:

> FYI I've seen this bug since 11.04
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1290055).
> https://bugs.launchpad.net/bugs/1286552
>
> Title:
> No wifi after suspend
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> After suspending ubuntu the wifi doesn't work. The solution given here
> (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re-
> connecting-after-suspend) worked for me but when I have updated my
> Ubuntu now it won't work. I have tried to test mainline kernel but it
> won't to boot with it.
>
> To reproduce the bug : just suspend the computer and then power it.
> There's no wifi network until you restart the computer.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: ubuntu-release-upgrader-core 1:0.205.4
> ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
> Uname: Linux 3.11.0-15-generic i686
> ApportVersion: 2.12.5-0ubuntu2.2
> Architecture: i386
> CrashDB: ubuntu
> Date: Sat Mar 1 15:20:39 2014
> InstallationDate: Installed on 2013-12-30 (61 days ago)
> InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386
> (20131017)
> MarkForUpload: True
> PackageArchitecture: all
> SourcePackage: ubuntu-release-upgrader
> Symptom: dist-upgrade
> UpgradeStatus: No upgrade log present (probably fresh install)
> ---
> ApportVersion: 2.12.5-0ubuntu2.2
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: meradi 1503 F.... pulseaudio
> DistroRelease: Ubuntu 13.10
> HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf
> InstallationDate: Installed on 2013-12-30 (61 days ago)
> InstallationMedia: Ubuntu-GNOME ...

I'm quite agree with Justin parker. Using an other app, instead the one by default, is not a solution. Just a workaround

I remember the time when evolution was default email-client and everybody was saying "use thunderbird instead". Or when someone complain about Brasero cause he just don't burn absolutely nothing, people answer "use k3b (and it's tons of dependencies) instead"

Anyway...

Using wicd ? Why not. BUT this program is quite deprecated now, isn't it ?? Last version in 2012.
And without speaking about the fact it won't be integrated to unity environnement at all....

I have an Asus X61SL laptop suffering from the same problem and I solved like this:
First use 'nmcli nm' to check the stats of the network manager, if its stats is asleep then all you have to do is this : 'sudo nmcli nm sleep false' and it will start working. To make the change permenant add the following script to '/etc/pm/sleep.d':

#!/bin/sh

case "${1}" in
        resume|thaw)
  nmcli nm sleep false
                ;;
esac

OssNass,

NM isn't stuck sleeping. It scans, recognizes the Wifi, tries to connect
but continually fails to do so. Over and over relentlessly.

On Tue, Apr 22, 2014 at 3:24 PM, OssNass <email address hidden> wrote:

> I have an Asus X61SL laptop suffering from the same problem and I solved
> like this:
> First use 'nmcli nm' to check the stats of the network manager, if its
> stats is asleep then all you have to do is this : 'sudo nmcli nm sleep
> false' and it will start working. To make the change permenant add the
> following script to '/etc/pm/sleep.d':
>
> #!/bin/sh
>
> case "${1}" in
> resume|thaw)
> nmcli nm sleep false
> ;;
> esac
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1290055).
> https://bugs.launchpad.net/bugs/1286552
>
> Title:
> No wifi after suspend
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> After suspending ubuntu the wifi doesn't work. The solution given here
> (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re-
> connecting-after-suspend) worked for me but when I have updated my
> Ubuntu now it won't work. I have tried to test mainline kernel but it
> won't to boot with it.
>
> To reproduce the bug : just suspend the computer and then power it.
> There's no wifi network until you restart the computer.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: ubuntu-release-upgrader-core 1:0.205.4
> ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
> Uname: Linux 3.11.0-15-generic i686
> ApportVersion: 2.12.5-0ubuntu2.2
> Architecture: i386
> CrashDB: ubuntu
> Date: Sat Mar 1 15:20:39 2014
> InstallationDate: Installed on 2013-12-30 (61 days ago)
> InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386
> (20131017)
> MarkForUpload: True
> PackageArchitecture: all
> SourcePackage: ubuntu-release-upgrader
> Symptom: dist-upgrade
> UpgradeStatus: No upgrade log present (probably fresh install)
> ---
> ApportVersion: 2.12.5-0ubuntu2.2
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: meradi 1503 F.... pulseaudio
> DistroRelease: Ubuntu 13.10
> HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf
> InstallationDate: Installed on 2013-12-30 (61 days ago)
> InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386
> (20131017)
> MachineType: Hewlett-Packard HP Compaq 6830s
> MarkForUpload: True
> Package: linux (not installed)
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic
> root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
> RelatedPackageVersions:
> linux-restricted-modules-3.11.0-15-generic N/A
> linux-backports-modules-3.11.0-15-generic N/A
> linux-firmware 1.116.2
> Tags: saucy
> Uname: Linux 3.11.0-15-generic i686
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugde...

I can confirm, nm is not asleep. I check it with "nmcli nm". It just doesn't connect...

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

Agreed NM not asleep.... I used to get a bad password error in 12.04 haven't seen that here

If the network manager is not asleep then try this, it might help
http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html

Is the problem present in KUbuntu or XUbuntu or it is just for Ubuntu ?

The output of "lshw -C network" and "nmcli nm" before and after the suspending might be usefull, so please can you submit that ?

Removing Jupiter (as in comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/comments/60 ) has solved the problem for me. Additionally, suspending is now back to pre-13.04 speeds on my Thinkpad X220 (i.e. under 2 seconds).

Suffered from the same Bug after upgrade 13.10 to 14.04

chipset:
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)

what caused the problem for me was an entry in /pm/config.d/modules
There module iwlwifi was suspendet
SUSPEND_MODULES="iwlwifi"

commenting out this line solved the problem for me permanentely (no more issues with suspend and awake). wifi is available instantely.

I can also confirm that my issue is resolved after removing /etc/pm/config.d/modules and a restart.

Affects me on 14.04, 3.13.0-24 kernel.

Network card: Intel Corporation Centrino Wireless-N 2230 (rev c4)
Module: iwlwifi

Seems solution in #68 solved the problem for me.
I installed 14.04 recently and suffered from this problem along with the other (often my Xubuntu failed to suspend/reboot/shutdown at all).
So the following steps let me comepletely get rid of these problems:
1. turn off Light Locker
2. uncheck All Settings -> Power Manager -> Extended -> Lock screen when going for suspend/hibernate
3. reboot
After all it looks to me like all the problems have the same roots related to Light Locker and screwed permissions.

I solved the issue by removing jupiter too

I don't even have jupiter installed on my system, so that's obviously not the issue.

I believe this problem is not a WIFI issue only - unless I have a new bug. My experience only started with 14.04 and the issue occurs on Wired Connection. Network Manager will not re-enable the network connection.

It works fine for me when plugged in. Definitely a wireless issue IME.
On May 3, 2014 6:35 PM, "kylea" <email address hidden> wrote:

> I believe this problem is not a WIFI issue only - unless I have a new
> bug. My experience only started with 14.04 and the issue occurs on Wired
> Connection. Network Manager will not re-enable the network connection.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1290055).
> https://bugs.launchpad.net/bugs/1286552
>
> Title:
> No wifi after suspend
>
> Status in “linux” package in Ubuntu:
> Confirmed
> Status in “network-manager” package in Ubuntu:
> Confirmed
>
> Bug description:
> After suspending ubuntu the wifi doesn't work. The solution given here
> (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re-
> connecting-after-suspend) worked for me but when I have updated my
> Ubuntu now it won't work. I have tried to test mainline kernel but it
> won't to boot with it.
>
> To reproduce the bug : just suspend the computer and then power it.
> There's no wifi network until you restart the computer.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: ubuntu-release-upgrader-core 1:0.205.4
> ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
> Uname: Linux 3.11.0-15-generic i686
> ApportVersion: 2.12.5-0ubuntu2.2
> Architecture: i386
> CrashDB: ubuntu
> Date: Sat Mar 1 15:20:39 2014
> InstallationDate: Installed on 2013-12-30 (61 days ago)
> InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386
> (20131017)
> MarkForUpload: True
> PackageArchitecture: all
> SourcePackage: ubuntu-release-upgrader
> Symptom: dist-upgrade
> UpgradeStatus: No upgrade log present (probably fresh install)
> ---
> ApportVersion: 2.12.5-0ubuntu2.2
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: meradi 1503 F.... pulseaudio
> DistroRelease: Ubuntu 13.10
> HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf
> InstallationDate: Installed on 2013-12-30 (61 days ago)
> InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386
> (20131017)
> MachineType: Hewlett-Packard HP Compaq 6830s
> MarkForUpload: True
> Package: linux (not installed)
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic
> root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
> RelatedPackageVersions:
> linux-restricted-modules-3.11.0-15-generic N/A
> linux-backports-modules-3.11.0-15-generic N/A
> linux-firmware 1.116.2
> Tags: saucy
> Uname: Linux 3.11.0-15-generic i686
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> WifiSyslog: Mar 1 15:34:33 meradi-HP-Compaq-6830s kernel: [
> 4581.474196] perf samples too long (5002 > 5000), lowering
> kernel.perf_event_max_sample_rate to 25000
> dmi.bios.date: 03/12/2009
> dmi.bios.vendor: Hewlett-Packard
> dmi.bios.ver...

Problem is back. Obviously not a modules file issue. Though I wonder why
removing it worked the first time around?
On May 3, 2014 6:52 PM, "Adam Hicks" <email address hidden> wrote:

> It works fine for me when plugged in. Definitely a wireless issue IME.
> On May 3, 2014 6:35 PM, "kylea" <email address hidden> wrote:
>
>> I believe this problem is not a WIFI issue only - unless I have a new
>> bug. My experience only started with 14.04 and the issue occurs on Wired
>> Connection. Network Manager will not re-enable the network connection.
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1290055).
>> https://bugs.launchpad.net/bugs/1286552
>>
>> Title:
>> No wifi after suspend
>>
>> Status in “linux” package in Ubuntu:
>> Confirmed
>> Status in “network-manager” package in Ubuntu:
>> Confirmed
>>
>> Bug description:
>> After suspending ubuntu the wifi doesn't work. The solution given here
>> (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re-
>> connecting-after-suspend) worked for me but when I have updated my
>> Ubuntu now it won't work. I have tried to test mainline kernel but it
>> won't to boot with it.
>>
>> To reproduce the bug : just suspend the computer and then power it.
>> There's no wifi network until you restart the computer.
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 13.10
>> Package: ubuntu-release-upgrader-core 1:0.205.4
>> ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
>> Uname: Linux 3.11.0-15-generic i686
>> ApportVersion: 2.12.5-0ubuntu2.2
>> Architecture: i386
>> CrashDB: ubuntu
>> Date: Sat Mar 1 15:20:39 2014
>> InstallationDate: Installed on 2013-12-30 (61 days ago)
>> InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386
>> (20131017)
>> MarkForUpload: True
>> PackageArchitecture: all
>> SourcePackage: ubuntu-release-upgrader
>> Symptom: dist-upgrade
>> UpgradeStatus: No upgrade log present (probably fresh install)
>> ---
>> ApportVersion: 2.12.5-0ubuntu2.2
>> Architecture: i386
>> AudioDevicesInUse:
>> USER PID ACCESS COMMAND
>> /dev/snd/controlC0: meradi 1503 F.... pulseaudio
>> DistroRelease: Ubuntu 13.10
>> HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf
>> InstallationDate: Installed on 2013-12-30 (61 days ago)
>> InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386
>> (20131017)
>> MachineType: Hewlett-Packard HP Compaq 6830s
>> MarkForUpload: True
>> Package: linux (not installed)
>> ProcFB: 0 radeondrmfb
>> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic
>> root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7
>> ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
>> RelatedPackageVersions:
>> linux-restricted-modules-3.11.0-15-generic N/A
>> linux-backports-modules-3.11.0-15-generic N/A
>> linux-firmware 1.116.2
>> Tags: saucy
>> Uname: Linux 3.11.0-15-generic i686
>> UpgradeStatus: No upgrade log present (probably fresh install)
>> UserGroups: adm cdrom dip lpadmin plugdev sam...

My issue was resolved after removing /etc/pm/config.d/config and a RESTART.

That config file contained the line SUSPEND_MODULES="wl", which I had added after the first time problems came up with suspend/resume about half a year ago (using 12.04) and using these instructions to fix it: http://ubuntuforums.org/showthread.php?t=2138927.

WORKS AGAIN NOW !

Does anyone know if Canonical or ubuntu developers will be trying to fix this or a duplicate of it, please?

None of the suggested fixes apply or have worked for me on 14.04. I won't be upgrading my other computer from 12.04 until this issue is fixed. (When I tried that computer on the 14.04 Live CD it also wouldn't reconnect to wifi after waking from suspend.) Rebooting the computer doesn't always even work for me, and not suspending it at all isn't very energy-saving. It pains me to say I find myself using Windows more these days as a result...

Finally found a fix that worked for me: http://askubuntu.com/a/368836

Also, at http://ubuntuforums.org/showthread.php?t=2218043, there was the following extra line in wakenet.sh:
pkill -f wpa_supplicant
...but I found I didn't need that. (But I'm posting that here in case someone else will need it.)

Works for me too.

sudo touch /etc/pm/sleep.d/wakenet.sh

sudo chmod +x /etc/pm/sleep.d/wakenet.sh

sudo gedit /etc/pm/sleep.d/wakenet.sh

Insert the following lines:

#!/bin/bash
case "$1" in
thaw|resume)
nmcli nm sleep false
pkill -f wpa_supplicant
;;
*)
;;
esac
exit $?

And then save.

At least the problem seems to be solved !!

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 and everything ran fine after this.

The problem seems to occur after kernel updates. NetworkManager needs to be restarted ('sudo kill PIDforNetworkManager") after suspend.

uname -r
3.13.0-36-generic
apt-cache policy network-manager
network-manager:
  Installed: 0.9.8.8-0ubuntu7
  Candidate: 0.9.8.8-0ubuntu7
  Version table:
 *** 0.9.8.8-0ubuntu7 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

*-network
       description: Wireless interface
       product: Centrino Wireless-N 1000 [Condor Peak]
       vendor: Intel Corporation

$ lsmod | grep intel
snd_intel8x0m 18830 0
snd_ac97_codec 130285 3 snd_via82xx_modem,snd_atiixp_modem,snd_intel8x0m
snd_hda_intel 56451 3
snd_hda_codec 192906 3 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel
snd_pcm 102099 7 snd_ac97_codec,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_via82xx_modem,snd_atiixp_modem,snd_intel8x0m
snd_page_alloc 18710 5 snd_pcm,snd_hda_intel,snd_via82xx_modem,snd_atiixp_modem,snd_intel8x0m
snd 69322 21 snd_ac97_codec,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_via82xx_modem,snd_seq_device,snd_atiixp_modem,snd_intel8x0m,snd_seq_midi

I've found that killing "NetworkManager" (note the caps) resolves the issue and restarts the NetworkManager applet. I can then select a wifi network & continue.

I run Ubuntu 14.04 on a DELL XPS 13 notebook. I started having this problem after I upgraded to kernel 3.13.0-37. Resume takes longer than usual and I need to kill NetworkManager in order to restart it and be able to get a connection.

#92 seems to have solved this bug for me. Thanks nknico. My Dad has the same bug on OSX...

Sorry spoke too soon, it worked with a brief period of suspend (screen did go blank) but is not working again. Tried #93 for what I thought might be the equivalent file no joy.

Seems to be working intermittently...

Wouldn't recommend the course of action in 92, I've broken wifi after reboot it won't connect, I'm going to have to reinstall the operating system.

I've found, as a work around, sending a "kill -hup" signal to the wpa_supplicant process will 'wake' it up and network connectivity will get restored again

Lenovo Thinkpad 520 with the same issue here....

T

The issue started recently (early November 2014). I had been running 14.04 since July without this issue. So an automatic update has infected my setup since early November.

The work around was to create the file 04_bug_network_manager_restart in directory /etc/pm/sleep.d. See terminal listing and script contents below. Its a pain but at least it hides the issue. Hopefully someone at Canonical will resolve the issue sometime soon.

$ ls -la /etc/pm/sleep.d/04_bug_network_manager_restart
-rwxr-xr-x 1 root root 334 Dec 12 22:12 /etc/pm/sleep.d/04_bug_network_manager_restart

$ cat /etc/pm/sleep.d/04_bug_network_manager_restart
#! /bin/sh
#
# after suspend restart network-manager
# http://askubuntu.com/questions/450688/network-connection-error-after-suspend-ubuntu-14-04
#

case "$1" in
 suspend)
 echo "do nothing"
  ;;

 hibernate)
 echo "do nothing"
  ;;

 resume)
 echo "network-manager restart"
 service network-manager restart
 ;;

 *) exit $NA
 ;;
esac

I see it on a laptop that does not connect automatically to the wireless network after wakeup. But I have the same issue also with a desktop with wired ethernet. So a more appropriate title would be 'network manager fails to reconnect after resume', because the issue is not wifi specific.

After a suspend/resume cycle, network manager does not reconnect.

For the desktop, given that this used to be a machine going to sleep when unused and being waken from the lan, the issue is pretty bad. The machine wakes... but with no network. Network manager stays there for ever, with the connection ready and selected for automatic connection, but does not even try to start the connection.

Since it completely breaks the usability of wol, please rise priority.

This is something recent. I have also started to see it about November. Furthermore, it used to work just fine with 14.04.

As a further note, the script by aztecjoe works around the issue just fine.

I would recommend delivering it via an updated network manager package and not waiting for network manager to have the issue fixed. If and when the issue is fixed in network manager, the redundant restart should not be a big issue.

I tracked down the issue where WiFi would fail after suspend in that it doesn't associate anymore (tries to connect but fails), and it's a bug in wpa-supplicant that was fixed in the current version (Ubuntu uses 2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's wpa-supplicant 2.3 and rebooting immediately fixed the issue. I know that at least some people here had this issue...

https://packages.debian.org/sid/wpasupplicant

the latest kernel seems to be working much better for be, as even after resume I get working wifi. Unfortunately it fails after a while again (without suspend or power save, just in the middle of surfing). Likely my issue this is now more related to i.e. Bug 1320070
Thanks for all your work.
PS: posting form Win-Partition :-((((

The solution in comment #92 worked for me and, in contrast with comment #91, for me it was essential to keep the "pkill -f wpa_supplicant" line. Using a Samsung NP530U3B laptop with 14.04.

same problem on a fresh ubuntu 14.04 on HP Pavilion 15. it's so annoying.

Solution is :

sudo touch /etc/pm/sleep.d/wakenet.sh

sudo chmod +x /etc/pm/sleep.d/wakenet.sh

sudo gedit /etc/pm/sleep.d/wakenet.sh

Insert the following lines:

#!/bin/bash
case "$1" in
thaw|resume)
nmcli nm sleep false
pkill -f wpa_supplicant
;;
*)
;;
esac
exit $?

And then save and exit.

> nicolas kleinklaus (nknico) wrote on 2015-07-01: #109
> Solution is :
>
> sudo touch /etc/pm/sleep.d/wakenet.sh
>
> sudo chmod +x /etc/pm/sleep.d/wakenet.sh
>
> sudo gedit /etc/pm/sleep.d/wakenet.sh
>
> Insert the following lines:
>
> #!/bin/bash
> case "$1" in
> thaw|resume)
> nmcli nm sleep false
> pkill -f wpa_supplicant
> ;;
> *)
> ;;
> esac
> exit $?
>
> And then save and exit.

Didn't help for me. However calling
    sudo modprobe -rf r8712u
before suspension and
    sudo modprobe r8712u
on wakeup helped.

still present in 15.10 :(

iwlwifi driver on Aspire 5930G and I solved in this way:
creating both /etc/pm/config.d/unload_modules and /etc/pm/sleep.d/wakenet.sh
the command that permit to connect wifi after resume is
sudo pkill -f wpa_supplicant

bye

is there any workaround resume script that is working for 15.10.+ and systemd?

Here is a solution that worked for me in Ubuntu 15.10: http://askubuntu.com/questions/754913/wifi-doesnt-reconnect-after-suspend-in-ubuntu-15-10-yet-again/754915#754915

sudo touch /lib/systemd/system-sleep/restart-networking.sh
sudo chmod +x /lib/systemd/system-sleep/restart-networking.sh
sudo nano /lib/systemd/system-sleep/restart-networking.sh

which contains:

#!/bin/sh
case "$1/$2" in
 post/*)
 echo "network-manager restart" >> /var/log/wakeup.log
 /bin/systemctl restart network-manager.service
 ;;
esac

Following works for me for my Sony Vaio (even when enabling energy saving option for ath9k driver). I collected the script information from various sources - the last missing thing for my Vaio seemed to be the timeout parameter. Since I added the timeout parameter it works:

case "$1" in

hibernate|suspend)
  nmcli nm sleep true
  sleep 1
  modprobe -rf ath9k
;;

thaw|resume)
  nmcli nm sleep true
  modprobe -rf ath9k
  nmcli nm sleep false --timeout 10
  modprobe ath9k
  killall wpa_supplicant
;;

*) exit $NA
;;
esac

same on Lenovo Y70-70 16.04LTS

Seeing the same problem on my Dell XPS13 (2016)

BTW,

If I do "sudo iwlist wlp58s0 scanning" when the problem is present my wifi starts working again.

/Jo Christian