Bug 206785 - Umlauts are locking backspace key in TUI dialog window
Summary: Umlauts are locking backspace key in TUI dialog window
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: newt
Version: 4.4
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Miroslav Lichvar
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-09-16 17:47 UTC by Robert Scheck
Modified: 2010-03-08 09:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-03-08 09:02:54 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Robert Scheck 2006-09-16 17:47:56 UTC
Description of problem:
When typing a umlaut e.g. a "ö" in the directory field at the http setup TUI 
dialog window, backspace key will be locked. Workaround is to click on "Back"
to get a usable http setup TUI dialog window during repeating the step.

The selected language setting was English with a German keyboard. As this is a 
common setting in Germany, this has to work, because "äöü" is near the "Enter" 
key and it's likely that umlauts are pressed by mistake.

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

How reproducible:
Everytime, see above.

Actual results:
Umlauts are locking backspace key in TUI dialog window.

Expected results:
No locking, normal use of backspace key to delete the umlaut.

Comment 1 Robert Scheck 2007-02-23 16:22:01 UTC
What's the current status? Do we get this fixed for Red Hat Enterprise Linux 5?

Comment 2 Robert Scheck 2007-05-08 19:06:16 UTC
This bug report is fixed for Fedora 7 (as per bug #206697), but is it also 
fixed for RHEL5?

Comment 3 Joel Andres Granados 2008-04-21 11:37:54 UTC
This bug is a newt issue.

Comment 4 RHEL Program Management 2008-10-31 16:49:41 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 5 Robert Scheck 2008-10-31 16:55:32 UTC
AFAIK this bug report already succeeded this flag internally. Please check the 
related case for that...

Comment 6 Miroslav Lichvar 2010-03-08 09:02:54 UTC
We are sorry for not addressing this issue in RHEL-4. As newt is not scheduled
for an update in RHEL-4.9, I'm closing this bugzilla as WONTFIX. If you are
still experiencing this issue with RHEL-5, please reopen it against RHEL-5.

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