Bug 1301174 - unable to delete input in appliance_console
Summary: unable to delete input in appliance_console
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.5.0
Hardware: All
OS: Linux
medium
low
Target Milestone: GA
: cfme-future
Assignee: Nick Carboni
QA Contact: luke couzens
URL:
Whiteboard: black
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-22 19:08 UTC by Colin Arnott
Modified: 2016-11-29 16:31 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-29 16:31:35 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Colin Arnott 2016-01-22 19:08:21 UTC
Description of problem:
In appliance_console after text is entered it cannot be deleted and the backspace key generates ^H in the text input.

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

How reproducible:
very

Steps to Reproduce:
1. run appliance_console
2. press enter and get to a text entry field
3. enter text
4. use backspace

Actual results:
^H character in inserted into text field

Expected results:
last character is deleted

Additional info:

Comment 2 Nick Carboni 2016-01-25 19:45:37 UTC
I can't reproduce this in an ssh session (terminal + bash), through the vsphere thick client, or using VMM on fedora.  With what option in the appliance console are you seeing this behavior and how are you accessing the console?  I suspect this is an issue with that particular system rather than the console itself.

Comment 3 Colin Arnott 2016-02-09 21:13:37 UTC
Sorry for the delay; I have reproduced the error and can confirm it is an issue with xterm specifically. Most Linux terminals emulate a VT200 terminal, but xterm targets VT100.

Let me know if this helps, or if you would like additional information.

Sources
0] http://ibb.net/~anne/keyboard.html#prob

Comment 5 Nick Carboni 2016-11-29 16:31:35 UTC
Closing this as it is an issue with a specific terminal rather than a bug in the console.


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