Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Propagate $TERM from PID 1 to bash prompt to make nspawn better #3697
systemd version the issue has been seen with
Steps to reproduce. Let's assume we have some chroot environment in /str with systemd (debian stretch with systemd 230 in my case). Let's also assume we work is some x terminal emulator, in my case this is konsole (sic!) from KDE. Now we type
Actual behavior. We will see that nano "ate" some output of systemd boot process. I. e. nano ate some info that was present in terminal.
Expected behavior. nano should not do this.
When I just start nano from konsole directly it doesn't eat anything.
It seems the cause is $TERM. If I type
Possibly related issue: #3115.