Networking stops after returning from suspend; must reboot

[Dan Gillmor]

Ubuntu 13.10; ThinkPad T430s

This has occurred several times, but not every time.

After going into suspend , upon waking up the machine the networking no longer works. It says disabled in the menu bar. Clicking "enable networking" doesn't do anything. I go into the Network applet, which says airplane mode is on; I turn it off. Still nothing.

Wired and wireless connections are the same -- no connection.

I'm forced to reboot to restore networking function.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-release-upgrader-core 1:0.205
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
CrashDB: ubuntu
Date: Tue Oct 22 07:05:27 2013
InstallationDate: Installed on 2013-10-13 (9 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to saucy on 2013-10-17 (4 days ago)
VarLogDistupgradeTermlog:

[Dan Gillmor (dan-gillmor)]

Mine appears a bit different, as it worked after a reboot.

On 10/22/2013 07:16 AM, Thaddäus Tintenfisch wrote:
> *** This bug is a duplicate of bug 1184262 ***
> https://bugs.launchpad.net/bugs/1184262
>
> ** This bug has been marked a duplicate of bug 1184262
> [logind] stuck in PrepareForSleep, causing network and other services to not resume
>

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

A reboot generally resolves this issue and almost everybody confirms this. The bug description of the linked report might be a bit outdated, because things have changed throughout the development cycle. However, the general problem (network manager not awaking after returning from suspend) still remains.

[Dan Gillmor (dan-gillmor)]

Thanks...will keep watching for fix.

On 10/22/2013 10:05 AM, Thaddäus Tintenfisch wrote:
> *** This bug is a duplicate of bug 1184262 ***
> https://bugs.launchpad.net/bugs/1184262
>
> A reboot generally resolves this issue and almost everybody confirms
> this. The bug description of the linked report might be a bit outdated,
> because things have changed throughout the development cycle. However,
> the general problem (network manager not awaking after returning from
> suspend) still remains.
>

--
Dan Gillmor
dangillmor.com/about
+1.650.868.7528

[Dan Gillmor (dan-gillmor)]

sudo nmcli nm sleep false

works for me.

Thanks!

On 10/22/2013 10:05 AM, Thaddäus Tintenfisch wrote:
> *** This bug is a duplicate of bug 1184262 ***
> https://bugs.launchpad.net/bugs/1184262
>
> A reboot generally resolves this issue and almost everybody confirms
> this. The bug description of the linked report might be a bit outdated,
> because things have changed throughout the development cycle. However,
> the general problem (network manager not awaking after returning from
> suspend) still remains.
>

--
Dan Gillmor
dangillmor.com/about
+1.650.868.7528

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

Dan Gillmor, 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>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one all the way at the bottom) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

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