Network down after resume

Bug #1235864 reported by Julien Olivier
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
systemd-shim (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

In Saucy, after resuming from suspend, the network is disabled.

WORKAROUND: Running "sudo restart network-manager" fixes the problem each time.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: network-manager 0.9.8.0-0ubuntu21
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Sun Oct 6 08:11:23 2013
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2010-09-15 (1116 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
IpRoute:
 default via 192.168.0.254 dev wlan2 proto static
 192.168.0.0/24 dev wlan2 proto kernel scope link src 192.168.0.11 metric 9
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
MarkForUpload: True
NetworkManager.state:
 [main]
 WirelessEnabled=true
 NetworkingEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to saucy on 2011-04-01 (918 days ago)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth2 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1
 wlan2 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.0 connected enabled enabled enabled enabled disabled

Revision history for this message
Julien Olivier (julo) wrote :
Revision history for this message
Adolfo Jayme Barrientos (fitojb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1234469, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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
penalvch (penalvch)
description: updated
affects: network-manager (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Julien Olivier (julo) wrote :

This is actually a dup of #1184262.

Revision history for this message
C de-Avillez (hggdh2) wrote :

@all: if you change the status of a bug, or mark/unmark it as a duplicate, please *explain*, in a comment, why you are doing it. Certainly, if you think this is a wrong duplicate, you have some reasoning that may help us understand what happened.

@julo: thank you for your comment when changing the dup. Could be a bit less terse thou ;-)

Revision history for this message
Julien Olivier (julo) wrote :

@ C de-Avillez: Sorry for the abruptly concise comment but I really didn't think it was necessary to say more. I'll keep that in mind for the next time though.

Revision history for this message
penalvch (penalvch) wrote :

Unmarked as a duplicate as this was initially marked a duplicate with no indication this is such. As well, if something is happening after a resume, this would indicate a kernel bug in a driver causing this, versus userspace. Please do not mark this a duplicate again unless you can make a precise technical analysis on what commit would be causing this issue.

Thank you for your understanding.

Revision history for this message
Liam Proven (lproven) wrote :

Happening to me as well on Toshiba Satellite Pro P300-1AY.

Looks like Bug #1212199 & Bug #1247468

Revision history for this message
penalvch (penalvch) wrote :

Liam Proven, 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.

Revision history for this message
UbUK (ubuk) wrote :

This bug affects me too on an Acer Aspire 5720 laptop. Running sudo restart network-manager works but it's a PITA having to do this every time the laptop wakes up from Suspend.

This problem did not exist on 13.04. It only appeared after upgrading to 13.10.

Revision history for this message
Alexander Karlstad (alexander.karlstad) wrote :

Same here. Suspending with «sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"» doesn't affect my network though, but my screen is also unlocked after resuming.

Revision history for this message
penalvch (penalvch) wrote :

Julien Olivier, 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 <replace-with-bug-number>

UbUK / Alexander Karlstad, in order to track your hardware, could you please file a new report via a terminal:
systemd-shim

affects: linux (Ubuntu) → systemd-shim (Ubuntu)
Revision history for this message
Julien Olivier (julo) wrote :

As I already said before in comment #5, this bug is actually a dupe of https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1184262, which is fixed. So, i confirm that this bug is now fixed with the latest development release. I just don't understand why the duplicate status has been reverted...

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.