Bug 696333

Summary: login prompt doesn't show inserted characters
Product: Red Hat Enterprise Linux 6 Reporter: James M. Leddy <james.leddy>
Component: initscriptsAssignee: initscripts Maintenance Team <initscripts-maint-list>
Status: CLOSED NOTABUG QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: gborsuk, notting, rstrode, sassmann
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 589888 Environment:
Last Closed: 2011-04-26 20:36:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 589888    
Bug Blocks:    

Comment 2 James M. Leddy 2011-04-13 20:43:01 UTC
bug 586040, was closed with a fix in initscripts. It looks like we have regressed in 9.03.22-1.el6.x86_64, which is in the 6.1 beta.

Comment 4 Bill Nottingham 2011-04-13 21:47:12 UTC
CCing plymouth maintainer. If you ssh in, is plymouth running at this time?

Comment 5 James M. Leddy 2011-04-14 19:12:21 UTC
(In reply to comment #4)
> CCing plymouth maintainer. If you ssh in, is plymouth running at this time?

Yes. is that normal?

I'm not certain this is the same issue, one point of difference is it looks like mingetty was started in the badly toggled state <echo off> and then toggled it for echo on for password, and then retoggled off, which is not the exact same as what customer is seeing. Also, they are rhgb off where the other bug only happens with rhgb.

customer tried plymouth:debug at the kernel command line but they did not see any /var/log/plymouth-debug.log

Specific behavior is:

1) boot up
2) login: root <-this behaves normally
3) password: password <- this is echoed when it should not be
4) every character must preceded by a return character to be registered. Any character not preceded by a return character is thrown out, so for example, directory listing is 

<ENTER>l<ENTER>s<ENTER><ENTER>

The enter enter being the return (the return has to be preceded by the return character :) Since everything else is thrown away, it could also be done as:

<ENTER>larry<ENTER>sanders<ENTER><ENTER>

I did not file this as a bug in mingetty because I don't think mingetty was rebased in 6.1

Comment 6 Bill Nottingham 2011-04-14 20:36:42 UTC
If you ssh in and run 'plymouth quit', does it behave?

Comment 8 James M. Leddy 2011-04-21 19:28:58 UTC
(In reply to comment #6)
> If you ssh in and run 'plymouth quit', does it behave?

Everything starts working again, except your password still gets echoed upon login.

Comment 9 Ray Strode [halfline] 2011-04-26 20:26:37 UTC
so it sounds like "plymouth quit" either isn't getting called during start up, or it's getting called but ignored by plymouthd.

- can you put plymouth:debug on the kernel command line and post /var/log/plymouth/plymouth-debug.log after doing your manual plymouth quit call?

- what's the output of

rpm -qV initscripts 

- is selinux enabled and enforcing? does booting with enforcing=0 make a difference?

- I assume this is booting to runlevel 3 by default?

Comment 10 James M. Leddy 2011-04-26 20:36:53 UTC
(In reply to comment #9)
> so it sounds like "plymouth quit" either isn't getting called during start up,
> or it's getting called but ignored by plymouthd.
> 
> - can you put plymouth:debug on the kernel command line and post
> /var/log/plymouth/plymouth-debug.log after doing your manual plymouth quit
> call?
> 
> - what's the output of
> 
> rpm -qV initscripts 
> 
> - is selinux enabled and enforcing? does booting with enforcing=0 make a
> difference?
> 
> - I assume this is booting to runlevel 3 by default?

Ray,

Thanks for your help. The customer mucked with some of the init script files. That was causing plymouth not to exit properly.