[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-11-28 Thread Dimitri John Ledkov
** Changed in: snapd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-11-25 Thread Mathew Hodson
** Changed in: snapd (Ubuntu Xenial) Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-11-18 Thread Dimitri John Ledkov
Installed snapd from proposed, rebooted, and /snap/bin is now in path of systemd-run unit Nov 18 18:25:26 well-monkey env[298]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin # dpkg-query -W snapd snapd 2.42.1+18.04 Prior to reboot it was not in PATH of a

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-07-04 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.24 --- systemd (237-3ubuntu10.24) bionic; urgency=medium [Dimitri John Ledkov ] * core: export environment when running generators. Ensure that manager's environment (including e.g. PATH) is exported when running

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-07-04 Thread Launchpad Bug Tracker
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) *

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-07-02 Thread Balint Reczey
** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-07-02 Thread Balint Reczey
Tested 229-4ubuntu21.22 on Xenial: ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo systemd-run /usr/bin/env [sudo] password for ubuntu: Running as unit run-r22d04a00a8304e2da719773bb14b6fb4.service. ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ journalctl -a | grep PATH Jul 02 14:31:04

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-28 Thread Dan Streetman
re: autopkgtests, a few failed, but I re-ran them and they passed on the re-run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-27 Thread Łukasz Zemczak
Hello Dan, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.22 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-27 Thread Balint Reczey
** Branch linked: lp:~rbalint/britney/autopkgtest-bionic-hint -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Balint Reczey
@mvo @xnox ok, so if I run unfixed systemd and fixed snapd and unfixed initramfs-tools /usr/local/... patch are missing when booting with initramfs: ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo systemd-run --pty --wait /usr/bin/env | grep PATH Running as unit: run-u69.service Press ^]

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Balint Reczey
@mvo thanks for the test! Nor @xnox or I could reproduce the problem of missing /usr/local/bin and /usr/local/sbin when booting with initramfs. I tried even downgrading snapd to 2.37.1+18.04 and systemd to 237-3ubuntu10.10 with no luck. I seems it is safe to go ahead with the snapd fix, too. --

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Michael Vogt
The PR to re-enable the generator: https://github.com/snapcore/snapd/pull/7031 and updates the test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title:

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Michael Vogt
When we disabled the generator in snapd we added a regression test (tests/main/snap-system-env): https://github.com/snapcore/snapd/pull/6470/files With the current systemd (not the one in -proposed) I get: ``` grep error: pattern not found, got: LANG=C.UTF-8

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Balint Reczey
The added Breaks: will ensure that the fixes are applied together. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units,

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Balint Reczey
@xnox we were investigating this in parallel :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Balint Reczey
The snapd and systemd fixes triggered LP: #1814355 together and I'm now investigating if the initiramfs fix for that 'regression' should be backported to Bionic, too. In that case I'll add a new Breaks: to the systemd upload. -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Dimitri John Ledkov
In effect, I'm saying that we need to (a) fix systemd as per this bug report (b) fix initramfs-tools (c) only then enable snapd env generator -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Dimitri John Ledkov
We have codepaths with and without initrd, which results in different environment that systemd starts up with. In bionic, initramfs-tools sets PATH to PATH=/sbin:/usr/sbin:/bin:/usr/bin In later releases, initramfs-tools sets PATH to

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Balint Reczey
The autopkgtest failures seem to be unrelated. I re-triggered flaky tests and I'm updating the hints where needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-26 Thread Balint Reczey
Verified 237-3ubuntu10.24 on Bionic: root@bb:~# systemd-run /usr/bin/env Running as unit: run-r14e6d7c0430841c59697a5c84ded2a88.service root@bb:~# dpkg -l systemd | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-25 Thread Brian Murray
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.24 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-25 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+merge/369298 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-25 Thread Balint Reczey
@jweede I uploaded the SRU fix again for Bionic and tried to reproduce the regression you observed but it works for me: ubuntu@ip-172-31-47-218:~$ uname -a Linux ip-172-31-47-218 4.15.0-1041-aws #43-Ubuntu SMP Thu Jun 6 13:39:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-172-31-47-218:~$

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-25 Thread Balint Reczey
** Description changed: [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

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-25 Thread Balint Reczey
@mvo /usr/lib/systemd/system-environment-generators/snapd-env-generator is working in Bosmic and up, but in Bionic it is not executable. Could this please be fixed? ** Changed in: snapd (Ubuntu Cosmic) Status: Confirmed => Fix Released -- You received this bug notification because you

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-25 Thread Balint Reczey
** Description changed: [Impact] - * This means that software installed via snap isn't transparently +  * 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

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-06-21 Thread Francis Ginther
** Tags added: id-5d0bec28939a024305398e2a -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-02-18 Thread Jamie Strandboge
FYI, this bug is marked Fix Committed against systemd for bionic, but there is currently nothing in bionic-proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-02-02 Thread Jon Wedaman
@xnox The grub config makes me believe the aws image is booted with initramfs. Thanks for responding, I wasn't sure if this was the right spot to report this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-02-02 Thread Dimitri John Ledkov
@jweede Hm. And is the instance booted with or without initramfs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units,

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2019-02-01 Thread Jon Wedaman
Just noticed what might be a regression from this fix. `/usr/local/sbin:/usr/local/bin` are now missing from unit on newest ubuntu bionic ami (us-east-1: ami-012fd5eb46f56731f) ubuntu@ubuntu:~$ dpkg-query -W systemd systemd 237-3ubuntu10.11 ubuntu@ubuntu:~$ sudo systemd-run /usr/bin/env Running

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-12-04 Thread Dimitri John Ledkov
Using systemd 237-3ubuntu10.10, executing the test case i see /snap/bin in path ubuntu@ubuntu:~$ dpkg-query -W systemd systemd 237-3ubuntu10.10 ubuntu@ubuntu:~$ sudo systemd-run /usr/bin/env [sudo] password for ubuntu: Running as unit: run-rc05da62ca3b445e4b3259a6a17063a61.service

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-11-19 Thread Łukasz Zemczak
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-10-08 Thread Dimitri John Ledkov
** Description changed: - This means that software installed via snap isn't transparently + [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. - Specifically,

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-10-05 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-09-29 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 239-7ubuntu9 --- systemd (239-7ubuntu9) cosmic; urgency=medium * core: export environment when running generators. Ensure that manager's environment (including e.g. PATH) is exported when running generators. Otherwise, one is at a

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-09-26 Thread Dimitri John Ledkov
Using this bug to fix systemd exported environment to the generators. ** Changed in: systemd (Ubuntu Cosmic) Status: Won't Fix => Fix Committed ** Changed in: systemd (Ubuntu Bionic) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-08-30 Thread Michael Vogt
This is being worked on in https://github.com/snapcore/snapd/pull/5736 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-08-28 Thread Dimitri John Ledkov
still not fixed in snapd. ** Changed in: snapd (Ubuntu Cosmic) Importance: Undecided => Critical ** Changed in: snapd (Ubuntu Cosmic) Assignee: (unassigned) => Michael Vogt (mvo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-06-18 Thread Robie Basak
I filed bug 1777445 for the non-interactive ssh case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-06-18 Thread Robie Basak
A related issue is that "ssh " currently fails because /snap/bin isn't in PATH. In that case, sshd sets PATH via pam_env. I'm not sure if a systemd environment generator will help with this use case or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-30 Thread Robert C Jennings
I'll mention this here because I believe it's related, if not please correct me and I'll file a separate bug. When cron jobs are run /snap/bin is not in the path. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-29 Thread Michael Vogt
https://github.com/snapcore/snapd/pull/5226 <- contians a PR for this now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for

Re: [Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-18 Thread Seth Arnold
On Fri, May 18, 2018 at 06:01:19PM -, Oliver Grawert wrote: > well, my subtle hint would point to simply add it to /etc/environment > here, which would globally cover for everything, would allow us to drop Note that /etc/environment is only used by PAM-aware services that have been configured

Re: [Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-18 Thread Dimitri John Ledkov
On 18 May 2018 at 19:01, Oliver Grawert wrote: > well, my subtle hint would point to simply add it to /etc/environment > here, which would globally cover for everything, would allow us to drop > the profile.d snippet in ubuntu images/installs and to my knowledge > would even be

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-18 Thread Oliver Grawert
well, my subtle hint would point to simply add it to /etc/environment here, which would globally cover for everything, would allow us to drop the profile.d snippet in ubuntu images/installs and to my knowledge would even be used by systemd (or am i wrong here ?) ... (and i think it would even

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-18 Thread Dimitri John Ledkov
re:single code path we do have a lot of duplication. I think profile.d is actually good enough for all the logged in users. However, for now, the /usr/lib/systemd/system-environment-generators is a special place to integrate and ensure that environment that systemd creates for units has

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-18 Thread Dimitri John Ledkov
/etc/profile.d is for the login shells. the bug is about the environment of systemd units as started by systemd. That environment is not created / does not parse /etc/profile.d this new integration is to fix the environment as seen by binaries spawned by systemd (e.g. cloud-init). Specifically

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-18 Thread Oliver Grawert
i meant to say above is that it would be nice to find a way that covers all use-cases with one code path (sorry, just noticed what i wrote wasnt clear in that regard) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in

[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH

2018-05-18 Thread Oliver Grawert
snapd ships a snippet in /etc/profile.d that sets the PATH to /snap/bin and should theoretically work for all login shells (except for zsh which doesn't respect the profile.d standard) ... bug 1640514 and bug 1659719 are related. -- You received this bug notification because you are a member of