This bug was fixed in the package systemd - 217-2ubuntu1 --------------- systemd (217-2ubuntu1) vivid; urgency=medium
* Merge with Debian unstable. See 217-1ubuntu1 for remaining Ubuntu changes. * Put session scopes into all cgroup controllers instead of their parent user slices. This works better with killing sessions and is consistent with the "systemd" controller. * Do not realize and migrate cgroups multiple times, in particular "-.slice". This fixes PIDs in non-systemd cgroup controllers to be randomly migrated back to /. (LP: #1346734) * boot-and-services autopkgtest: Give test apparmor job some time to actually finish. systemd (217-2) experimental; urgency=medium * Re-enable journal forwarding to syslog, until Debian's sysloggers can/do all read from the journal directly. * Fix hostnamectl exit code on success. * Fix "diff failed with error code 1" spew with systemd-delta. (Closes: #771397) * Re-enable systemd-resolved. This wasn't meant to break the entire networkd, just disable the new NSS module. Remove that one manually instead. (Closes: #771423, LP: #1397361) * Import v217-stable patches (up to commit bfb4c47 from 2014-11-07). * Disable AppArmor again. This first requires moving libapparmor to /lib (see #771667). (Closes: #771652) * systemd.bug-script: Capture stderr of systemd-{delta,analyze}. (Closes: #771498) -- Martin Pitt <martin.p...@ubuntu.com> Mon, 01 Dec 2014 17:17:30 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1397361 Title: Failed to try-restart systemd-resolved.service: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs