So in systemd-shim3.log StartUnit('suspend.target') is called once,
while in systemd-shim2.log it's called twice. Are you sure that systemd-
shim2.log was the one where things worked properly? It seems much more
likely to me that calling StartUnit('suspend.target') twice in short
succession might cause problems.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

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

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

Reply via email to