This bug was fixed in the package systemd - 229-4ubuntu21.22 --------------- systemd (229-4ubuntu21.22) xenial; urgency=medium
[ Dan Streetman ] * d/t/systemd-fsckd, d/t/cmdline-upstart-boot: - skip on s390x; requires grub (LP: #1830477) * d/p/ask-password-prevent-buffer-overrow-when-reading-fro.patch: - prevent buffer overflow when reading keyring (LP: #1814373) [ Dimitri John Ledkov ] * Specify Ubuntu's Vcs-Git [ Balint Reczey ] * Append /snap/bin to default PATH. Snapd ships snapd-env-generator, but systemd does not not support environment generators. Hard-coding /snap/bin is less risky than backporting environment generator support and since snaps are considered to be first class packages on Ubuntu /snap/bin can safely added to the default PATH. (LP: #1771858) [ Ioanna Alifieraki ] * d/p/systemctl-Replace-check_one_unit-by-get_state_one_un.patch - Backport upstream PR#2768 needed for next patch * d/p/systemctl-load-unit-if-needed-in-systemctl-is-active.patch - Backport upstream PR#7997 to fix alias service reports inactive while aliased is active (LP: #1828892) -- Dan Streetman <ddstr...@canonical.com> Wed, 24 Apr 2019 17:15:36 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Invalid Status in systemd source package in Xenial: Fix Released Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Released Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp