Description of problem: I set a couple of environment variables by creating ~/.config/environment.d/00.conf with the following contents: PATH=$PATH:$HOME/.cargo/bin RUST_SRC_PATH=$HOME/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src NVIM_GTK_DOUBLE_BUFFER=1 NVIM_GTK_NO_HEADERBAR=1 NVIM_GTK_PREFER_DARK_THEME=1 BASE16_THEME=ocean All of these variables are set correctly on session start, except the PATH variable which always ends up having some kind of a default value /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin "systemctl --user show-environment" shows the intended PATH variable correctly: /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/YaLTeR/.cargo/bin I am using GDM and running the latest git sway, although the issue also manifests with the GNOME session. Sway has a debug mode where it dumps some environment variable values on start and indeed the PATH variable is already wrong when sway starts, so it's not a sway issue. I looked for configs and scripts that could override PATH everywhere but I did not find anything. I am assuming this is a GDM issue, but I'm not really sure what component is responsible for this behavior. Version-Release number of selected component (if applicable): gdm-3.30.1-2.fc29 How reproducible: Always Steps to Reproduce: 1. Create ~/.config/environment.d/00.conf with the following contents: PATH=$PATH:$HOME/something/whatever 2. Reboot Actual results: The PATH variable does not contain $HOME/something/whatever Expected results: The PATH variable contains $HOME/something/whatever Additional info: I'm starting sway with the following /usr/share/wayland-sessions/sway.desktop: [Desktop Entry] Name=Sway Comment=SirCmpwn's Wayland window manager Exec=sway Type=Application
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Seems to be a GNOME bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/385 Still present in Fedora 32 with Gnome 3.36.