Hello again!
I just made some progress: I tracked this down to agetty settings in
the container:
When I add --autologin USER to the agetty command line in
container-getty@.service, then the return key stops working.
I am not 100% sure, but I think that is due to magic in agetty: When
reading
Hi Lennart,
sorry, this took a bit longer than expected, but I took the time to
upgrade to systemd 221, so the results should be a bit closer to the
current state than before (which was still using systemd 219).
Inside container (broken shell/fish):
speed 38400 baud; rows 60; columns 184; line
Thanks for the reply!
I'll try to collect all requested info tonight or over the weekend.
Best Regards,
Tobias
On Thu, Jun 18, 2015 at 9:24 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Tue, 26.05.15 21:40, Tobias Hunger (tobias.hun...@gmail.com) wrote:
This is stty -a from outside
On Tue, 26.05.15 21:40, Tobias Hunger (tobias.hun...@gmail.com) wrote:
This is stty -a from outside the container:
speed 38400 baud; rows 46; columns 114; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = M-^?;
eol2 = M-^?; swtch = undef; start = ^Q;
stop = ^S; susp =
Lennart,
this apparently is a problem with machinectl login: If I just use
nsenter --target PID --mount --uts --ipc --net
as root the return key works fine.
TERM=xterm with nsenter (no surprise considering that I run that from
a xterm;-), while it is vt220 in machinectl.
Any ideas?
Best
This is stty -a from outside the container:
speed 38400 baud; rows 46; columns 114; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = M-^?;
eol2 = M-^?; swtch = undef; start = ^Q;
stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O;
min = 1; time = 0;
On Sat, 23.05.15 00:09, Tobias Hunger (tobias.hun...@gmail.com) wrote:
Hello,
I am having a problem with one of my containers set up with
systemd-nspawn. For some reason the return key will not work most of
the time (19 out of 20 attemps) after doing machinectl login into that
machine.
