| 2018-05-17 16:25:51 |
Dan Watkins |
bug |
|
|
added bug |
| 2018-05-17 16:26:10 |
Dan Watkins |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-05-17 16:26:10 |
Dan Watkins |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-05-18 13:33:40 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Bionic) |
|
| 2018-05-18 13:33:45 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Xenial) |
|
| 2018-05-18 13:33:55 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Cosmic |
|
| 2018-05-18 13:33:55 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Cosmic) |
|
| 2018-05-18 14:11:50 |
Dimitri John Ledkov |
description |
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. |
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.
Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). |
|
| 2018-05-18 14:17:53 |
Dimitri John Ledkov |
description |
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.
Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). |
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.
Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.).
Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment.
E.g.:
$ sudo mkdir -p /usr/lib/systemd/system-environment-generators
$ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user.
Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. |
|
| 2018-05-18 14:18:00 |
Dimitri John Ledkov |
bug task added |
|
snapd (Ubuntu) |
|
| 2018-05-18 14:18:14 |
Dimitri John Ledkov |
systemd (Ubuntu Cosmic): status |
New |
Won't Fix |
|
| 2018-05-18 14:18:17 |
Dimitri John Ledkov |
systemd (Ubuntu Bionic): status |
New |
Won't Fix |
|
| 2018-05-18 14:18:19 |
Dimitri John Ledkov |
systemd (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2018-05-18 14:19:01 |
Dimitri John Ledkov |
description |
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.
Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.).
Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment.
E.g.:
$ sudo mkdir -p /usr/lib/systemd/system-environment-generators
$ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user.
Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. |
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.
Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.).
Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment.
E.g.:
$ sudo mkdir -p /usr/lib/systemd/system-environment-generators
$ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user.
Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up.
systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. |
|
| 2018-05-18 14:19:27 |
Dimitri John Ledkov |
summary |
/snap/bin not in default PATH for units |
/snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH |
|
| 2018-05-18 14:21:31 |
Dimitri John Ledkov |
description |
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.
Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.).
Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment.
E.g.:
$ sudo mkdir -p /usr/lib/systemd/system-environment-generators
$ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user.
Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up.
systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. |
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.
Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.).
Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment.
E.g.:
$ sudo mkdir -p /usr/lib/systemd/system-environment-generators
$ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user.
Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up.
systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there.
[Testcase]
$ systemd-run /usr/bin/env
$ journalctl -e | grep PATH
Output should contain /snap/bin |
|
| 2018-05-30 13:23:16 |
Launchpad Janitor |
snapd (Ubuntu): status |
New |
Confirmed |
|
| 2018-05-30 13:23:16 |
Launchpad Janitor |
systemd (Ubuntu): status |
New |
Confirmed |
|
| 2018-05-30 13:23:16 |
Launchpad Janitor |
snapd (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2018-05-30 13:23:16 |
Launchpad Janitor |
snapd (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2018-05-30 13:24:36 |
Robert C Jennings |
bug |
|
|
added subscriber Robert C Jennings |
| 2018-06-18 13:10:40 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2018-08-28 16:19:09 |
Dimitri John Ledkov |
snapd (Ubuntu Cosmic): importance |
Undecided |
Critical |
|
| 2018-08-28 16:19:17 |
Dimitri John Ledkov |
snapd (Ubuntu Cosmic): assignee |
|
Michael Vogt (mvo) |
|
| 2018-09-26 09:57:54 |
Dimitri John Ledkov |
systemd (Ubuntu Cosmic): status |
Won't Fix |
Fix Committed |
|
| 2018-09-26 09:57:58 |
Dimitri John Ledkov |
systemd (Ubuntu Bionic): status |
Won't Fix |
Confirmed |
|
| 2018-09-29 23:18:44 |
Launchpad Janitor |
systemd (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2018-10-05 13:52:11 |
Dimitri John Ledkov |
systemd (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2018-10-08 10:08:38 |
Dimitri John Ledkov |
description |
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.
Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.).
Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment.
E.g.:
$ sudo mkdir -p /usr/lib/systemd/system-environment-generators
$ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user.
Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up.
systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there.
[Testcase]
$ systemd-run /usr/bin/env
$ journalctl -e | grep PATH
Output should contain /snap/bin |
[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]
$ 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. |
|
| 2018-11-19 14:03:05 |
Łukasz Zemczak |
systemd (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-11-19 14:03:09 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-11-19 14:03:11 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-11-19 14:03:14 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-bionic |
|
| 2018-12-04 12:19:50 |
Dimitri John Ledkov |
tags |
verification-needed verification-needed-bionic |
verification-done verification-done-bionic |
|
| 2019-02-01 20:57:28 |
Jon Wedaman |
bug |
|
|
added subscriber Jon Wedaman |
| 2019-06-21 12:38:54 |
Francis Ginther |
tags |
verification-done verification-done-bionic |
id-5d0bec28939a024305398e2a verification-done verification-done-bionic |
|
| 2019-06-25 10:18:02 |
Balint Reczey |
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]
$ 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. |
[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 it is not
$ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator
# reboot or run systemctl-daemon-reload, 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. |
|
| 2019-06-25 10:18:19 |
Balint Reczey |
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 it is not
$ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator
# reboot or run systemctl-daemon-reload, 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. |
[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 or run systemctl-daemon-reload, 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. |
|
| 2019-06-25 10:28:55 |
Balint Reczey |
snapd (Ubuntu Cosmic): status |
Confirmed |
Fix Released |
|
| 2019-06-25 10:31:05 |
Balint Reczey |
bug |
|
|
added subscriber Balint Reczey |
| 2019-06-25 14:09:47 |
Balint Reczey |
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 or run systemctl-daemon-reload, 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. |
[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 or run systemctl daemon-reload, 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. |
|
| 2019-06-25 14:11:49 |
Balint Reczey |
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 or run systemctl daemon-reload, 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. |
[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. |
|
| 2019-06-25 14:48:49 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+merge/369298 |
|
| 2019-06-25 23:47:39 |
Brian Murray |
tags |
id-5d0bec28939a024305398e2a verification-done verification-done-bionic |
id-5d0bec28939a024305398e2a verification-needed verification-needed-bionic |
|
| 2019-06-26 07:32:40 |
Balint Reczey |
tags |
id-5d0bec28939a024305398e2a verification-needed verification-needed-bionic |
id-5d0bec28939a024305398e2a verification-done-bionic verification-needed |
|
| 2019-06-27 10:21:45 |
Balint Reczey |
branch linked |
|
lp:~rbalint/britney/autopkgtest-bionic-hint |
|
| 2019-06-27 15:34:43 |
Łukasz Zemczak |
systemd (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2019-06-27 15:34:52 |
Łukasz Zemczak |
tags |
id-5d0bec28939a024305398e2a verification-done-bionic verification-needed |
id-5d0bec28939a024305398e2a verification-done-bionic verification-needed verification-needed-xenial |
|
| 2019-07-02 14:23:32 |
Balint Reczey |
snapd (Ubuntu Xenial): status |
Confirmed |
Invalid |
|
| 2019-07-02 14:30:20 |
Balint Reczey |
tags |
id-5d0bec28939a024305398e2a verification-done-bionic verification-needed verification-needed-xenial |
id-5d0bec28939a024305398e2a verification-done verification-done-bionic verification-done-xenial |
|
| 2019-07-03 08:08:13 |
Mathew Hodson |
bug |
|
|
added subscriber Mathew Hodson |
| 2019-07-04 09:18:32 |
Launchpad Janitor |
systemd (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-07-04 09:18:42 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-07-04 09:20:16 |
Launchpad Janitor |
systemd (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2019-11-18 18:26:48 |
Dimitri John Ledkov |
tags |
id-5d0bec28939a024305398e2a verification-done verification-done-bionic verification-done-xenial |
id-5d0bec28939a024305398e2a verification-done verification-done-xenial verification-needed-bionic |
|
| 2019-11-18 18:27:00 |
Dimitri John Ledkov |
tags |
id-5d0bec28939a024305398e2a verification-done verification-done-xenial verification-needed-bionic |
id-5d0bec28939a024305398e2a verification-done verification-done-bionic verification-done-xenial |
|
| 2019-11-18 18:27:06 |
Dimitri John Ledkov |
snapd (Ubuntu Bionic): status |
Confirmed |
Fix Committed |
|
| 2019-11-18 18:27:11 |
Dimitri John Ledkov |
snapd (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2019-11-26 06:24:46 |
Mathew Hodson |
snapd (Ubuntu Xenial): status |
Invalid |
Won't Fix |
|
| 2019-11-28 13:23:18 |
Dimitri John Ledkov |
snapd (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-12-03 00:42:16 |
Mathew Hodson |
removed subscriber Mathew Hodson |
|
|
|
