Bug 35254

Summary: miscompiled: term keys (not even BS/DEL/^H) not working
Product: [Retired] Red Hat Linux Reporter: j. alan eldridge <alane>
Component: bashAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED NOTABUG QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-04-08 21:55:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description j. alan eldridge 2001-04-08 21:55:28 UTC 
Only tested in X. No terminal keys functional. Suspect misconfiguration[0]
or missing libs on build machine[1].  Replaced with bash-2.04-21[2] from
rawhide, which works fine.

[0]I haven't checked the src rpm spec file for weirdness yet. Will followup
if anything noteworthy turns up. (It's kinda hard to miscompile bash, since
it takes so much of its configuration into its own hands, but I guess
anything's possible.)

[1]FWIW nslookup on wolverine exhibits the same
annoying-to-the-point-of-uselessness problem with control keys. 

[2]This uses the same shared libs, per ldd output, as the wolverine
package, further supporting suggestion of a misconfigured build machine.
Comment 1 j. alan eldridge 2001-04-08 22:13:51 UTC 
****NOTE**** I was NOT clear above. Please read following before responding.

The problem does not exist on the bash command line. The problem only exists
when executing the "read" builtin.  It *does* seem to be terminal dependent. 

I'm closing this and will reopen an issue once I really know what's going on.
Sorry for the false alarm.