Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #717282 +++
Description of problem:
tcsh has some troubles with printing sequences of wide (eg. 'ö') and single-byte ASCII characters (eg. 'a') using LANG=C.
Steps to Reproduce:
1. Set LANG=C
2. Start tcsh
3. Type a wide character (eg. 'ö')
4. Type any single-byte ASCII character (eg. 'a')
Actual results:
The single character is printed 6 times instead of just once. For example when "öa" is typed, "aaaaaa" is printed.
Expected results:
The single character shall be printed just once, as expected.
Additional info:
The bug was revealed in bug 676305 comment 5.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Created attachment 734633[details]
Extracted upstream patch
This bug was fixed in upstream in tcsh-6.17.03. Attached solution extracted from upstream patch.
Comment 8RHEL Program Management
2013-10-14 01:03:55 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 12David Kaspar // Dee'Kej
2016-01-08 14:00:55 UTC
Comment on attachment 734633[details]
Extracted upstream patch
The patch is working and solves the issue. However, please note that the solution might be different than expected...
1) export LANG=C
2) ./tcsh
3) writing some wide-character (for our example lets use the already mentioned ö)
It will result in showing the escape sequence:
> \303\266
This is a different behaviour compared to e.g. bash (which will print the ö character instead). I have confirmed with upstream that this is a correct and currently designed behaviour. [See http://mx.gw.com/pipermail/tcsh/2016-January/004961.html]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0938.html