[Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume

[Ian Nicholson]

On 10/30/2013 04:59 AM, Martin Pitt wrote:
> We have one theory what the problem could be (shim times out before finishing the method call). To test this, it would be great if affected people could install the systemd-shim version from my PPA: https://launchpad.net/~pitti/+archive/sru-test:
>    
>    sudo add-apt-repository ppa:pitti/sru-test
>    sudo apt-get update
>    sudo apt-get upgrade
>
>    There are no other packages in it at the moment, so it's safe to
> upgrade. If you only want this specific package, grab one of these
> (depending on your architecture):
>
>    https://launchpad.net/~pitti/+archive/sru-test/+files/systemd-shim_3%2Breal-0ubuntu1pitti1_i386.deb
>    https://launchpad.net/~pitti/+archive/sru-test/+files/systemd-shim_3%2Breal-0ubuntu1pitti1_amd64.deb
>
> and install with "sudo dpkg -i /path/to/downloaded/package/systemd-
> shim_*.deb".
>
> Do you still get the problem with this? Does it behave any different?
>
> ** Package changed: network-manager (Ubuntu) => systemd-shim (Ubuntu)
>
> ** Changed in: systemd-shim (Ubuntu)
>         Status: Confirmed => Incomplete
>
This seems to have resolved the bug for me as well.

-- 
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/1184262

Title:
  [logind] stuck in PrepareForSleep, causing network and other services
  to not resume

Status in “systemd” package in Ubuntu:
  Confirmed
Status in “systemd-shim” package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume, network-manager claimed that wireless was not
  available and would not let me reconnect to the wireless here.
  'iwlist wlan1 scan' would also not work; so thinking that it was a
  driver problem, I rebooted the system.  When it came back up, nm-
  applet in lightdm claimed that networking was disabled, and the option
  to enable it was greyed out.  It could also not be enabled by nmcli.
  I ended up stopping network-manager, bringing up the interface via
  /etc/network/interfaces, and logging in... at which point, restarting
  network-manager *did* let me enable networking from my logged-in
  session.

  So there are several problems here:
   - after a reboot, network-manager claimed networking was disabled.
   - nm-applet is not letting me enable networking from the lightdm session.
   - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session.

  The last issue probably *was* a kernel driver problem; but the first
  two issues are network-manager problems of some kind.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu8
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sat May 25 21:38:31 2013
  InstallationDate: Installed on 2010-09-24 (974 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan1 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan1  scope link  metric 1000 
   192.168.1.0/24 dev wlan1  proto kernel  scope link  src 192.168.1.106 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=false
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago)
  WifiSyslog:
   
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files
   Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING         VERSION    STATE           NET-ENABLED   WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
   not running     unknown    unknown         unknown       unknown         unknown    unknown         unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions