I've found out that `/etc/environment.d` is not intended for setting
environment variables for login shells. From poettering at
https://github.com/systemd/systemd/issues/12938:
@dschepler is right. systemd-environment-d-generator gets run by
systemd --user, and thus set environment variables f
To add to the issue, `/etc/environment` has one line setting `PATH` and
throwing out any old versions of `PATH` (it doesn't contain `$PATH`).
Changing that changed my `PATH` consistently on reboot:
$ cat /etc/environment
PATH="/opt/ghc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
The issue you describe seems different from the upstream bug you
referenced, could be worth opening another systemd upstream issue
report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861363
Title:
My `/etc/profile` doesn't seem to set the PATH, so the systemd bug
resolution may not be applicable:
$ grep PATH /etc/profile
$
I have Ubuntu 18.04 (Server, I assume) installed on a cloud server. I
access it only via SSH/Mosh and have no GUI (X or Wayland) installed as
far as I know.
I'
Thank you for your bug report. In what session is the issue happening? The
upstream comments suggest it's wayland session specific?
Also how is /etc/profile setting up PATH for you?
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you
