error message with ssh logon into zsh session

pillmuncher

It's only a very small annoyance, but when I login with ssh into a zsh session, I get this error message:

/usr/share/defaults/etc/profile.d/50-history.sh:5: command not found: shopt

I think this line in 50-history.sh:

shopt -s histappend

should look something like this, maybe:

if [[ "$SHELL" == */zsh ]]; then
    setopt append_history
else
    shopt -s histappend
fi

TraceyC

I've got a pull request in review that will fix this error.

pillmuncher

TraceyC Thank you for the update.

But now I ran into another minor snag: The locale isn't set automatically anymore when I ssh into my other machine (both run Solus). I'm not sure if that's how it's supposed to be, but anyway the fix is easy enough. Just add this to the relevant Host sections in your local ~/.ssh/config:

SendEnv LANG LC_*

and make sure the server accepts it by adding this to its /etc/ssh/sshd_config:

AcceptEnv LANG LC_*

TraceyC

pillmuncher

The issue you're seeing with ssh is not related to the zsh config changes. The previous error with shopt was due to a zsh misconfiguration. This current error is due to how sshd is configured (as you've seen).

Please open an issue (if there isn't one already) on our bug tracker for this. By opening an issue, it will allow our developers to look into possibly adding the proper settings to the sshd config file, and allow you to keep track of progress. Thanks.

Staudey

TraceyC Seems to me to be because of this:

https://github.com/getsolus/packages/pull/3431/files#diff-dba32fb08487893118d78bf92ad1501c9e3f58d8f78390f59b3da0be8de3ead7R14-R16

Shouldn't that source /usr/share/defaults/etc/profile.d/10-xdg.sh instead?

TraceyC

Staudey /usr/share/defaults/etc/profile.d/10-xdg.sh

Ah, good catch. This PR was even reviewed heh. I've submitted a new PR to fix that - https://github.com/getsolus/packages/pull/4321

This has been merged. The fix is now available in unstable, and will be available in stable after the next sync. Let me know if that fixes the issue on your system, @pillmuncher , without the addition to ./ssh/config