Bug 676305 - Using tcsh, xterm ignores 14 keypresses after umlauf
Summary: Using tcsh, xterm ignores 14 keypresses after umlauf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: tcsh617
Version: 5.6
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Vojtech Vitek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-09 12:48 UTC by Ashish Shah
Modified: 2018-11-14 15:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, when the "LANG" environment variable was set to "C", tcsh could ignore several characters that were following a wide (greater than 8 bits) character while receiving user's input. This package fixes the issue and tcsh no longer ignores any characters.
Clone Of:
Environment:
Last Closed: 2011-07-21 08:48:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Patch based on upstream comment (767 bytes, patch)
2011-02-09 12:48 UTC, Ashish Shah
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 717282 0 unspecified CLOSED Printing troubles of wide and single-byte character sequences using LANG=C 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2011:1072 0 normal SHIPPED_LIVE new package: tcsh617 2011-07-21 08:47:46 UTC

Internal Links: 717282

Description Ashish Shah 2011-02-09 12:48:29 UTC
Created attachment 477795 [details]
Patch based on upstream comment

Description of problem:
While using tcsh shell, typing an Umlaut e.g. ö in xterm makes it ignore the next 14 keypresses (e.g. a)

After the next keypress it echoes \366

evebe788 - mayerg - /home/mayerg - (/bin/tcsh) 105$: \366


Version-Release number of selected component (if applicable):

tcsh-6.14-17.el5_5.2

How reproducible:

Always

Steps to Reproduce:

- German Keyboard
- LANG "C"
- xterm &
- Type ö

Yes, I I want to use LANG C, as I believe this works best with about our
100 commercial and in-house applications.
  
Actual results:

After Umlaut ( ö ) next 14 keypresses are ignored and then for the next keypress it echoes \366

Expected results:

- Just ignore the umlaut
- when i type the next character (e.g. a) after umlaut, echo a
- i don`t mind if it beeps to remind me there is an issue regaring 8bit
characters and/or using C locale


Additional info:

thanks to ofourdan for tracing the issue/patch
http://mx.gw.com/pipermail/tcsh/2006-November/003788.html

Comment 5 Branislav Náter 2011-06-24 12:56:16 UTC
Character typed after ö is printed 6 times. e.g. when "öa" is typed, "aaaaaa" is printed.

Comment 8 Vojtech Vitek 2011-06-28 08:44:27 UTC
The upstream patch for this issue (accepted in tcsh-6.15.00) fixes the reported issue - silently "eat" 14 characters after typing a wide characters while using LANG=C.

But the QA team found out during the usage testing, that the fix reveals another weird behaviour - after some wide characters, the shell now prints few more characters than expected.

Comment 12 Vojtech Vitek 2011-06-28 14:15:57 UTC
See bug 717282 for the related printing issue (mentioned in comment 5), that is actually caused by wrong printing of wide and single-byte ASCII character sequences.

Comment 13 Branislav Náter 2011-06-28 14:34:38 UTC
Bugfix was verified on tcsh617-6.17-5.el5 package.

Umlaut character doesn't cause ignoring following 14 key strokes now, but prints following character 6 times (see comment 5). This will be solved in separated bug 717282.

Comment 14 Miroslav Svoboda 2011-07-01 21:58:14 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, when the "LANG" environment variable was set to "C", tcsh could ignore several characters that were following a wide (greater than 8 bits) character while receiving user's input. This package fixes the issue and tcsh no longer ignores any characters.

Comment 15 errata-xmlrpc 2011-07-21 08:48:48 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-1072.html

Comment 16 errata-xmlrpc 2011-07-21 12:09:45 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-1072.html


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