Description of problem:
When RHEL6 beta is installed using the minimal install option, the keyboard arrows/tab do not display correctly. For example, if I type "chk" and then hit tab, the cursor jumps to the right about 8 spaces and I do not see any tab completion.
Hitting up arrow should show me the history, but all I see is ^[[A the down arrow gives me ^[[B.
Version-Release number of selected component (if applicable):
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
This is fallout from a problem in the patch in bug 582265
Note this bug also causes usernames to show up hidden and passwords to show up visible on tty1 when logging in.
This was actually fixed in plymouth-0.8.3-1.el6. After installing it, make sure to rebuild your initrd by installing a kernel or running /usr/libexec/plymouth/plymouth-update-initrd
Installing 0.8.3 is confirmed as fixing both login password being displayed as well as the tab completion.
Something is funny here. I'm going to need to do another build.
Should be fixed in plymouth-0.8.3-2.el6
I think what happened was:
1) At some point I added the patch to the source tree and did a local build and verified it.
2) I then got distracted by some other issue and forgot about it
3) Then this bug came along I went to my cvs checkout and saw the patch was already applied, wrote comment 5 and moved to MODIFIED, not realizing it wasn't built in brew yet.
What I don't understand is how plymouth-0.8.3-1.el6 fixes the problem for those hit by it.
Anyway, we definitely need the patch, so I've built -2 now.
Sorry for the confusion and mistakes.
*** Bug 591386 has been marked as a duplicate of this bug. ***
Tested and Verified after clean minimal install on plymouth-0.8.3-17.el6.x86_64, moving to VERIFIED.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.