[Pkg-shadow-devel] Bug#476519: Bug#476519: shell-mode garbles input
jidanni at jidanni.org
jidanni at jidanni.org
Fri May 2 16:30:02 UTC 2008
Here we see the typical deal. You asked me about ulimit. I tried to
get a shell oh, six times this time before the magic hand stopped
logging me out. Whereupon it bites off the first character of what I
type and logs me out, saving the message for after the next prompt.
Then I get a shell again to give you the answer.
# su - nobody
No directory, logging in with HOME=/
nobody at jidanni2:/$ logout
# su - nobody
No directory, logging in with HOME=/
nobody at jidanni2:/$ logout
# su - nobody
No directory, logging in with HOME=/
nobody at jidanni2:/$ logout
# su - nobody
No directory, logging in with HOME=/
nobody at jidanni2:/$ logout
# su - nobody
No directory, logging in with HOME=/
nobody at jidanni2:/$ logout
# su - nobody
No directory, logging in with HOME=/
nobody at jidanni2:/$ ulimit
logout
# su - nobody
bash: limit: command not found
# No directory, logging in with HOME=/
nobody at jidanni2:/$ ulimit
unlimited
nobody at jidanni2:/$ stty
speed 38400 baud; line = 0;
erase = <undef>; kill = <undef>;
-brkint -imaxbel
-onlcr
-echo
Happens also in xterm, where
# stty
speed 38400 baud; line = 0;
-brkint -imaxbel iutf8
SC> Does that happen straight away or after a delay?
The logout happens instantaneously, no waiting for me to type my first
command as nobody.
SC> The "logout" thing looks a bit like eof from the terminal.
Very much so.
SC> strace would probably help then:
No. Every time I use strace I get a shell that sticks around. The bug
is not triggered. I'll send you one anyway.
SC> And look at the last read(0 in /tmp/strace.out
SC> Could be a tty setting as well.
SC> stty min 0 time 10 -icanon
Ho ho ho, that even eats through all the shells stacked up in my emacs
shell buffer exiting each one.
SC> With readline
Has readline. I'll send you shopt output.
More information about the Pkg-shadow-devel
mailing list