Does not connect (to wired network) after suspend

[Marius Hofert]

I work with Xubuntu 12.04 on a MacBook Air 4,1. I can easily connect to the internet (wired network / auto ethernet), but after I put the laptop to sleep/suspend, nm-applet is gray and I can't connect to the internet anymore. Rebooting solves the problem. This seemed to be related up to the fact that it was a wireless connection (which always worked fine for me): https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/704756

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager-gnome 0.9.4.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Fri Jul 20 20:33:05 2012
EcryptfsInUse: Yes
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IpRoute:
 default via 178.83.94.1 dev eth1 proto static
 169.254.0.0/16 dev eth1 scope link metric 1000
 178.83.94.0/23 dev eth1 proto kernel scope link src 178.83.94.48 metric 1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth1 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/2
 eth2 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1
 eth0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.4.0 connected enabled enabled disabled enabled disabled

[Kai Mast (kai-mast)]

I have a similar issue in saucy on both of my machines.

"sudo restart network-manager" fixes the problem for me.

[Launchpad Janitor (janitor)]

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

[Alberto Salvia Novella (es20490446e)]

Kai Mast, are you using a MacBookAir too?

[Chris Cheney (ccheney)]

I'm also seeing this on saucy on a gigabyte ga-965p-dq6 motherboard with a marvell 88e8056 gige controller.

[Kai Mast (kai-mast)]

Alberto, no I am using a self build pc and a lenovo thinkpad edge.

This seems to be independent of the hardware

[Kai Mast (kai-mast)]

The following just happened to me.

Suspend/resume -> network manager broke (as expected)
Suspend/resume a second time -> network manager works again

[Chris Cheney (ccheney)]

I forgot to add all I have to do on saucy to fix the problem is service network-manager restart like Kai Mast as well. It appears to happen every time I suspend.

[Kai Mast (kai-mast)]

I still have this problem in saucy.

It says "triaged" but the bug is assigned to know one. Is anybody working on this? Do you need any more information?

[A. Richard Miller (themillers)]

Thank you! This solved my problem permanently - at least, for today. :-)

Using Saucy (64-bit Ubuntu Desktop 13.10 beta2) with daily updates, my Acer AO722 notebook computer had been networking well after suspending by closing its lid - until something changed less than a week ago. Beginning then, both wifi (Atheros AR9485) and wired networking would fail after the FIRST suspend, and never recovered without a reboot.

Today I read this thread, closed the lid to suspend, resumed (with networking now disabled) and tried "sudo restart network-manager" just once. It reconnected my wifi immediately. What's more, following that one use of that command line, repeated suspends retain my network connection even after powerdowns! I have not applied that CL a second time.

My network connection again stays solid. That seems better than others have reported. But so far, so good!

[A. Richard Miller (themillers)]

Drat! My "permanent fix" was working while I resumed operation within a few seconds after the Suspend LED began blinking. But several minutes of Suspend is enough to derail it, requiring another application of "sudo restart network-manager".

So, add me (and Saucy on an Acer AO722) to the list of those who await a permanent fix for this ongoing problem. Thanks for the work you do!

[panther_d (dk-mailbox)]

Got the same issue after updating to Saucy yesterday.

Restarting NetworkManager helps, but that's not a real option especially for non-computer-literate users...

[panther_d (dk-mailbox)]

I have a workaround that isn't particularly elegant but does the trick for me: have the NetworkManager automatically restart at resume.

1. add file to /etc/pm/sleep.d/ , e.g. call it 99_restart-network-manager, and make it executable
2. in the file, put
#!/bin/bash

case "${1}" in
    resume|thaw)
 restart network-manager
;;
esac

[A. Richard Miller (themillers)]

Thanks, panther_d. Much appreciated!

I'd considered doing something like that. But, like you, I want Saucy Salamander to "just work" for casual users of Ubuntu. Rather than featuring this bug, I'm delaying introducing Saucy Salamander to our clients and my FOSS User Group (NatickFOSS.org).

I hope that relief arrives soon! Please, Ubuntu/Canonical?

[Horst Schirmeier (horst)]

I'm seeing this on saucy, too. "service network-manager restart" fixes the problem. I'm using a Dell Latitude E6400 with iwlwifi.

[Chris Cheney (ccheney)]

This happens to me on saucy on two computers fairly often and a third seldomly.

The first system with the problem has a:

03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 14)

The other system has:

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

The system that mostly works has:

00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

[Peng (pengwg)]

Just for some input I have tested the mainline 3.8 kernel under saucy and the problem still occurs. Since I didn't have this problem in raring so maybe it's not kernel bug.

[penalvch (penalvch)]

Peng, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Horst Schirmeier (horst)]

This issue disables both wired and wireless connections, and it only happens about every second suspend/resume cycle on my machine. For the remaining cycles, networking comes back up fine after resume.

If the original bug reporter does not reply, I'm willing to follow the testing instructions Christopher posted.

[penalvch (penalvch)]

Horst Schirmeier, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[A. Richard Miller (themillers)]

Hi, Chris and All:

Great that this bug is active again!

My computer and my FOSS User Group use of Ubuntu are still limping with this failing Suspend (since a late beta of Saucy; see messages #10, 11, and 14 above), so I await a fix and invite you to ask when I can be of further help.

And, these further observations:
1. When Suspend fails, it fails with any of the following: with the closing of the lid, or by clicking on the Power button (in upper right of top bar) > Suspend, or by a Suspend time-out.
2. "sudo restart network-manager" will repair the problem - until I close the lid (for more than perhaps 20 seconds), or otherwise force a Suspend, or until I close the next session.
3. No such problems when using current Linux Lite instead of current Ubuntu Saucy!

[A. Richard Miller (themillers)]

Corrected version of "these further observations", above:
1. In a new session, Suspend will fail with any of the following: with the closing of the lid, or by clicking on the Power button (in upper right of top bar) > Suspend, or by a Suspend time-out.
2. "sudo restart network-manager" will repair the problem - until I close the lid (for more than perhaps 20 seconds), or otherwise attempt to Suspend or Shut Down the session. But sometimes I CAN close the lid to Suspend anyway; I haven't been able to identify what conditions are different.
3. No such problems when using current Linux Lite instead of current Ubuntu Saucy!Item 2 should be changed to end with, "or otherwise attempt to force a Suspend or Shut Down, or until I open the next session."

Also, this bug causes the unsuspecting or forgetful user to leave the "suspended" computer running until the bottom becomes very hot to the touch with potential harm to the hardware, or until the battery is fully discharged.

[A. Richard Miller (themillers)]

Sorry; this replaces my messages #22 and #23.

Hi, Chris and All:

Great that this bug is active again!

My computer and my FOSS User Group use of Ubuntu are still limping with this failing Suspend (since a late beta of Saucy; see messages #10, 11, and 14 above), so I await a fix and invite you to ask when I can be of further help.

And, these further observations:
1. In a new session, Suspend will fail with any of the following: with the closing of the lid, or by clicking on the Power button (in upper right of top bar) > Suspend, or by a Suspend time-out.
2. "sudo restart network-manager" will repair the problem - until I close the lid (for more than perhaps 20 seconds), or otherwise attempt to Suspend or Shut Down the session. But sometimes I CAN close the lid to Suspend anyway; I haven't been able to identify what conditions are different.
3. No such problems when using current Linux Lite instead of current Ubuntu Saucy!

Note that this bug causes the unsuspecting or forgetful user to leave the "suspended" computer running until the bottom becomes very hot to the touch with potential harm to the hardware, or until the battery is fully discharged.

[penalvch (penalvch)]

A .Richard Miller, it would be most helpful if you file a new report in a terminal so that your hardware may be reviewed:
ubuntu-bug linux

[penalvch (penalvch)]

Marius Hofert, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Kai Mast (kai-mast)]

Imo this is not a duplicate. The other bug is marked as fixed in trusty but I still have this problem -- also in trusty.

Sometimes I also need to restart nm-applet to reconnect.

[penalvch (penalvch)]

Kai Mast, if you have a problem in Trusty, please file a new report via a terminal:
ubuntu-bug linux

[A. Richard Miller (themillers)]

Christopher, I (a) didn't know quite how to comment on your comment #25 above, (b) had unclear results for a few days, and (c) was off on other matters.

However, today I downloaded the new patch by Martin Pitt (see parallel bug 1184262), and am delighted to report that all my Suspend problems have been gone during many tests over about 8 hours! Here's hoping that speads to a more general fix for all users.

[Syafix Said (zhavick)]

i'm using ubuntu 16.10, after suspend / sleep the notebook, then can't connect to wireless.
the only things is i can do is kill the nm-applet using System Monitor then run nm-applet again.
the wireless list will be shown,

Really need update information for 16.10.

[penalvch (penalvch)]

Syafix Said, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]