Note to Ryan and myself: For the final fix we should not just make the
timeout longer, as that would still cause a resume failure when
suspending for more than 10 minutes (in my PPA case), but completely
disable the timeout while a method call is being executed. That might
help for a few more people here (or perhaps even most of them).

** Also affects: systemd (Ubuntu Saucy)
   Importance: Undecided
       Status: New

** Also affects: systemd-shim (Ubuntu Saucy)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Trusty)
   Importance: Undecided
       Status: Invalid

** Also affects: systemd-shim (Ubuntu Trusty)
   Importance: High
     Assignee: Martin Pitt (pitti)
       Status: In Progress

** Changed in: systemd (Ubuntu Saucy)
       Status: New => Invalid

** Changed in: systemd-shim (Ubuntu Saucy)
       Status: New => Triaged

** Changed in: systemd-shim (Ubuntu Saucy)
   Importance: Undecided => High

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

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

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to