Bug 81553

Summary: German umlauts and bash on console or via ssh
Product: [Retired] Red Hat Linux Reporter: Björn Gerhart <gerhart>
Component: bashAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: high Docs Contact:
Priority: high    
Version: 8.0CC: mitr
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:51:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Björn Gerhart 2003-01-10 13:09:57 UTC
Description of problem:
When I type in some chars and delete them
with backspace everything is fine. The same done with german
umlauts (e.g. üöä) causes that backspace can delete chars behind
the leftmost: the promt can be deleted also. So for every umlaut
TWO chars can be deleted.

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


How reproducible:
* German-latin1 keyboard is loaded
* bash is the login shell
* error happens on text console or ssh connection

Steps to Reproduce:
1) go to a text console (_no_ console within X!)
2) enter "loadkeys de-latin1-nodeadkeys"
3) type _one_ German umlaut (ä, ö, ü or Ã)
4) press <backspace> two times
    
Actual results:
The cursor enters a position which is not allowed. Its position is within the
prompt.

Expected results:
After the second press of <backspace> the cursor must not go further to the left.

Additional info:
* When entering an umlaut-key on the user login, the character is not shown
correctly; two special characters are shown instead of one umlaut

Comment 1 Miloslav Trmac 2003-01-10 14:17:17 UTC
Duplicate of bug 74925, fixed in rawhide.

Comment 2 Tim Waugh 2003-01-10 19:19:30 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 18:51:04 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.