You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting user services, some environment variables that should be present and available to the services being started are filtered out by openrc. This causes observable breakage in some scenarios, such as opening Yakuake on a Plasma session.
The environment variables that are important and currently left out are HOME, USER and SHELL, however we should probably pass the entire user environment as-is to the services (since it comes from PAM env + login shell as far as I've understood - so it's identical to what an user would get upon login)
The text was updated successfully, but these errors were encountered:
HOME is not being filtered, but USER and SHELL are
since it comes from PAM env + login shell as far as I've understood - so it's identical to what an user would get upon login
not quite, since calling rc-service foo start from a shell would import that shell's enviroment. and even at login, i'm unsure if random environment variables from the user's .profile should go through at all
noting system services do load /etc/profile.env though
When starting user services, some environment variables that should be present and available to the services being started are filtered out by openrc. This causes observable breakage in some scenarios, such as opening Yakuake on a Plasma session.
The environment variables that are important and currently left out are
HOME
,USER
andSHELL
, however we should probably pass the entire user environment as-is to the services (since it comes from PAM env + login shell as far as I've understood - so it's identical to what an user would get upon login)The text was updated successfully, but these errors were encountered: