FS#67369 - [pam] pam_env doesn't set environment variables from ~/.pam_environment
Attached to Project:
Arch Linux
Opened by nl6720 (nl6720) - Thursday, 23 July 2020, 08:25 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 13 August 2020, 09:39 GMT
Opened by nl6720 (nl6720) - Thursday, 23 July 2020, 08:25 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 13 August 2020, 09:39 GMT
|
Details
Description:
After upgrading to pam 1.4.0-2 and pambase 20200721.1-1, environment variables from ~/.pam_environment are not set anymore. Not in getty nor in a graphical Plasma X11 session started from SDDM. Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any pam 1.4.0-2 pambase 20200721.1-1 Steps to reproduce: $ echo TEST1 DEFAULT="1" >> ~/.pam_environment relogin $ printenv TEST1 |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Thursday, 13 August 2020, 09:39 GMT
Reason for closing: Fixed
Additional comments about closing: pambase-20200721.1-2 pam-1.4.0-3
Thursday, 13 August 2020, 09:39 GMT
Reason for closing: Fixed
Additional comments about closing: pambase-20200721.1-2 pam-1.4.0-3
Edit:
Upstream further clarified the reason for the change [2].
[1] https://github.com/linux-pam/linux-pam/commit/f83fb5f25263356391d71da595def409e8dd90f7
[2] https://github.com/linux-pam/linux-pam/commit/cbdef051ab5d4031656d14ac6cdb1f6c2d8d6595