Bugzilla – Bug 1085771
.bashrc no longer evaluated on ssh remote login
Last modified: 2018-03-19 14:13:11 UTC
Since update to TW 20180313, if I do a remote login to this machine via ssh, my $HOME/.bashrc is no longer evaluated, I'm missing all fuctions/aliases/variables defined there. 20180312 (on another machine) is still fine.
(probably related to openssh update, I wasn't sure if that should go to 'Security', but it's not really a security threat...)
Hmm, seems it's not ssh related: My Root windows
(xterm +sm -bg LightGoldenrod -geometry 120x24 -ls -vb -T Root -e su - )
also don't read roots .bashrc anymore, so it must be related to the '-ls' login shell that (AFAIK) also ssh uses.
Very annoying :(
I usually solve this having
[[ -x ~/.bashrc ]] && . ~/.bashrc
in ~/.bash_profile (or replacing .bash_profile with it entirely, or symlinking it to .bashrc).
Anyway, I'd close this bug as invalid (the behaviour is actually correct, and the one you report as prior, is wrong).
Gah. And this 'bug' is found after how many decades?
And then 'fixed' without mentioning it in the changelogs?
Fact is, 'bash -l' for bash-4.4-103.1 *does* read ~/.bashrc, like all the versions before did, and bash-4.4-103.2 no longer does.
Hmm, the 'needinfo' was by accident?
Nevertheless, I opened a 'proper' report against bash: