Bug 206318 - xterm-192-4.EL4 and Exceed
Summary: xterm-192-4.EL4 and Exceed
Keywords:
Status: CLOSED DUPLICATE of bug 212998
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: xterm
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Miroslav Lichvar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-13 17:03 UTC by Dora Abdullah
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-11-16 14:33:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dora Abdullah 2006-09-13 17:03:15 UTC
Description of problem:

The problem occurs when connecting via Hummingbird Exceed v.10 to a Linux
machine with Kernel 2.6.9-42.ELsmp that has xterm-192-4.EL4. Once an XTerm
window is opened, the Backspace key mapping breaks. It cannot be set via the
following stty either:
 stty erase ^H
 stty erase '^?'

Note that the problem does not exist when connecting to a Linux machine with
Kernel 2.6.9-34.X that has xterm-192-1 using the same connection method and user
login.

Version-Release number of selected component (if applicable):
xterm-192-4.EL4

How reproducible:

Using Hummingbird Exceed v.10 via "Secure Shell" method and "xterm" command. 

Steps to Reproduce:
1. Using Exceed's Secure Shell method, connect to a Linux machine with Kernel
2.6.9-42.ELsmp and has xterm-192-4.EL4.
2. Backspace key no longer works, nor can it be set via stty erase.
3.
  
Actual results:


Expected results:


Additional info: The problem does not exist when connecting to a Linux machine
with Kernel 2.6.9-34.X that has xterm-192-1 using the same connection method and
user login.

Comment 1 Miroslav Lichvar 2006-11-16 14:33:10 UTC
The problem is probably caused by backarrowKey resource, which was changed in
the last update.

To fix it, delete line "*VT100*backarrowKey: false" in file
/usr/X11R6/lib/X11/app-defaults/XTerm.

*** This bug has been marked as a duplicate of 212998 ***


Note You need to log in before you can comment on or make changes to this bug.