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
In d33487c#diff-abf7d6e1d74604f159aeaaf38a3f3b3aR962 (when setting auto-login to console), the TERM option passed to agetty are taken from the current user's session - the one that runs raspi-config. This can produce incorrect results for the console auto-login session if raspi-config is executed remotely and the TERM is set to something like xterm-256color.
This produces an autologin.conf containing
ExecStart=-/sbin/agetty --autologin pi --noclear %I xterm-256color
instead of
ExecStart=-/sbin/agetty --autologin pi --noclear %I $TERM
The console session (via auto-login) should have TERM=linux. I think $TERM should be escaped to \$TERM to avoid the variable substitution.
The text was updated successfully, but these errors were encountered:
Confirming. Replacing xterm-256color with $TERM in /etc/systemd/system/getty@tty1.service.d/autologin.conf solved the problem with strange dialog characters.
In d33487c#diff-abf7d6e1d74604f159aeaaf38a3f3b3aR962 (when setting auto-login to console), the
TERM
option passed toagetty
are taken from the current user's session - the one that runsraspi-config
. This can produce incorrect results for the console auto-login session ifraspi-config
is executed remotely and theTERM
is set to something likexterm-256color
.This produces an autologin.conf containing
instead of
The console session (via auto-login) should have
TERM=linux
. I think$TERM
should be escaped to\$TERM
to avoid the variable substitution.The text was updated successfully, but these errors were encountered: