[Bug 1234469] Re: Network does not come up after resuming from suspend.

[Catalin Hritcu]

*** This bug is a duplicate of bug 1184262 ***
    https://bugs.launchpad.net/bugs/1184262

I've tried suggested by pitti. After the first suspend and resume I get this:
Lid closed.
Suspending...
Failed to send delayed message: Message did not receive a reply (timeout by message bus)
Lid opened.

Networking was disabled so I brought it back up with "nmcli nm sleep
false". Then I suspended again. After the second suspend trying to
resume just led to another suspend I didn't ask for. Had to force
another resume (power button) before the thing actually resumed:

Lid closed.
Suspending...
Failed to execute operation: Message did not receive a reply (timeout by message bus)
Suspending...
Operation finished.
Lid opened.

Earlier today it happened to me that I couldn't resume at all because of
this problem happening many times in a row. I would get to the login
prompt but the machine would go back to sleep so fast that I wouldn't
even have time to enter my password. I had to power off and restart the
machine to take it out of that state. I'm on a Dell Latitude E6400.

BTW. Should I stop commenting here and switch to #1184262 instead?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1234469

Title:
  Network does not come up after resuming from suspend.

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “systemd” package in Ubuntu:
  Confirmed

Bug description:
  When my computer wakes up from being suspended, the wireless network connection doesn't come back up.
  I'm able to fix the problem by running "nmcli nm sleep false", which causes the wireless card to reconnect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu21
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  2 20:21:33 2013
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-09 (54 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.125.1 dev wlan0  proto static 
   192.168.125.0/24 dev wlan0  proto kernel  scope link  src 192.168.125.8  metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
   	Soft blocked: no
   	Hard blocked: no
  SourcePackage: network-manager
  SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
  UpgradeStatus: Upgraded to saucy on 2013-08-09 (54 days ago)
  nmcli-con:
   NAME                      UUID                                   TYPE              TIMESTAMP    TIMESTAMP-REAL                     AUTOCONNECT   READONLY   DBUS-PATH                                 
   Wired connection 1        99a6c07f-9a94-4c8e-82dd-0381befd6f90   802-3-ethernet    1380753272   Wed 02 Oct 2013 05:34:32 PM CDT    yes           no         /org/freedesktop/NetworkManager/Settings/1
   9739                      172c6f5c-b69c-40dd-ac1b-a279c84a17f8   802-11-wireless   1380763079   Wed 02 Oct 2013 08:17:59 PM CDT    yes           no         /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE     TYPE              STATE         DBUS-PATH                                  
   eth0       802-3-ethernet    unavailable   /org/freedesktop/NetworkManager/Devices/1  
   wlan0      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         enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1234469/+subscriptions