https://bugs.kde.org/show_bug.cgi?id=505529
Jannik Glückert <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Jannik Glückert <[email protected]> --- I can confirm this issue, let me summarize why this is a real bummer: Systemd provides various facilities for packages, system administrators, and users to customize the user env. Namely simple snippets in environment.d and env generators (used by flatpak, for example). However, this is only active once the user session starts. startplasma-wayland, however, obviously starts outside of the session via sddm. This means that startplasma-wayland If I understand https://invent.kde.org/plasma/plasma-workspace/-/blob/master/startkde/startplasma-wayland.cpp correctly, startplasma-wayland basically does: 1. eval plasma-workspace/env scripts 2. set some misc required env vars like XDG_SESSION_TYPE 3. export this env into the systemd session - roughly equivalent to `systemctl --user import-environment` 4. re-import the env from the systemd session, and use this for the desktop session This is completely broken though. It means that the env that startplasma-wayland was launched with will always override env vars set through the standardized systemd mechanisms. Namely, we can't set PATH now, since the original startplasma-wayland env certainly has this set. I think plasma should do something like: 1. set known constant envs in the systemd session (such as XDG_SESSION_TYPE) 2. import the systemd session. 3. run plasma-workspace/env scripts 4. export the updated env to the systemd session For now, I'll just have to run plasma-workspace with this env export patched out :/ -- You are receiving this mail because: You are watching all bug changes.
