maemo.org Bugzilla – Bug 6045
ENTER key stops working in XTerm
Last modified: 2011-02-06 03:53:52 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
1. Open XTerm.
2. SSH to some external machine.
3. Run SCREEN on that external machine.
4. Disconnect SSH session.
ENTER key continues working in XTerm.
ENTER key is not working. You have to close XTerm and start it again.
EXTRA SOFTWARE INSTALLED:
The server is running
Screen version 4.00.03 (FAU) 23-Oct-06
I saw this yesterday and had to use Ctrl-M to send newlines.
I have this as well. When my connection goes down (everything still looks
connected, however, see bug 5708 for details), ssh terminates, saying "Timeout,
server not responding." (I have ServerAliveInterval=60 set in my .ssh/config to
help mitigate bug 5708 by keeping the wifi alive) and I'm left at the shell
prompt. Pressing Enter does nothing, I have to press CTRL-M to get a carriage
I can reproduce this 100% of the time.
I think that this is related to bug 6009.
What I think happens here is that screen issues a terminal initialization
sequence which enables the application numeric keypad mode and makes the
KP_Enter key send \033OM.
I strongly believe that osso-xterm (or, vte, probably) should internally treat
KP_Enter as the regular Enter key, making it always send \n (even in
application keypad mode).
(In reply to comment #3)
> I strongly believe that osso-xterm (or, vte, probably) should internally treat
> KP_Enter as the regular Enter key, making it always send \n (even in
> application keypad mode).
I agree and add to this that resolving the following bug would let the user
reset osso-xterm if something like that happens:
*** This bug has been confirmed by popular vote. ***
(In reply to comment #4)
> I agree and add to this that resolving the following bug would let the user
> reset osso-xterm if something like that happens:
That bug is definitely fixed internally as I can reset the terminal.
I also think that this depends on bug 6009 - adding dep.
This bug was reported against 1.2009.41-10 and there have been two software
updates since then.
Can you please try/report if the issue here still happens in version
(In reply to comment #7)
> Can you please try/report if the issue here still happens in version
It still happens in 2.2009.51-1.
Thanks for retesting.
If the cause is that the SSH connection dies while being in application mode
(to reproduce, you can close the connection with the two characters "~." after
a Ctrl-M), then this is not a bug (except the consequence of bug 6009). You'll
notice that the Enter key isn't necessarily the only affected key. Depending on
the shell and its configuration, the arrow keys may no longer work as well
(because the escape sequences are not the same in application mode). This is
not specific to Maemo. Same problem everywhere.
Instead of restarting the terminal, you can reset it with the "reset" utility
(after the prompt, type "reset" then Ctrl-M).
Please retest this with the Community SSU from:
I'm assuming that this bug (Enter key stops working) is fixed by the patch that
fixes bug 6009, and that patch is included in the vte package from the
Community SSU (see bug 6009 for details).
moreinfo as per last quesion.
I confirm that the Community SSU fixes the problem.
Thanks for retesting!
For others reading this report: See bug 6009 and
http://wiki.maemo.org/Community_SSU for more information how to receive the