Network Manager disabled after wake from suspend

[James Kemp]

Same as bug #1242679 when I resume from suspend networking is disabled. I can use the workarounds on CLI to re-enable it, but only on CLI with sudo. I cannot get it working using the panel applet.

Happy to collect more info if required to aid diagnosis.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-13-generic 3.11.0-13.20
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: james 1892 F.... pulseaudio
Date: Tue Nov 12 20:58:13 2013
HibernationDevice: RESUME=UUID=cd49a4ff-7acd-4847-ac8b-b42ae8264971
InstallationDate: Installed on 2013-10-17 (25 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: SAMSUNG ELECTRONICS CO., LTD. Q320/P320
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=f357f8ec-e723-45bd-9abf-4eec43663a82 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-13-generic N/A
 linux-backports-modules-3.11.0-13-generic N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-10-21 (21 days ago)
WifiSyslog:

dmi.bios.date: 05/19/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01LH.M008.20090519.KSY
dmi.board.name: Q320/P320
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr01LH.M008.20090519.KSY:bd05/19/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnQ320/P320:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnQ320/P320:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: Q320/P320
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[James Kemp (james+ubuntu)]

NB I followed the instructions in the comments for the referenced bug. Not quite sure you guys want duplicate bug reports, but not for me to reason why.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

[Launchpad Janitor (janitor)]

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