Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 591386 - VT swallows keys
VT swallows keys
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: plymouth (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Ray Strode [halfline]
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2010-05-12 01:39 EDT by Qian Cai
Modified: 2010-05-22 15:40 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-22 15:40:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
initramfs (11.87 MB, application/octet-stream)
2010-05-14 01:08 EDT, Qian Cai
no flags Details
initramfs (12.17 MB, application/octet-stream)
2010-05-22 11:48 EDT, Qian Cai
no flags Details

  None (edit)
Description Qian Cai 2010-05-12 01:39:28 EDT
Description of problem:
When login from a VT, several previous typed keys are discarded (without any sign on the screen) before it accepts the input for username/password.

Version-Release number of selected component (if applicable):
RHEL6 public beta 1 x86_64

How reproducible:
Comment 1 Qian Cai 2010-05-12 02:46:53 EDT
It behaved strangely. Sometimes, it did not accept ENTER key only. If it started in runlevel 5, and then switched back to VT, everything was working fine.
Comment 2 Qian Cai 2010-05-12 05:16:51 EDT
This looks like a KMS bug since it went away by adding nomodeset on both ATI and Intel graphic systems.
Comment 3 Qian Cai 2010-05-12 05:36:22 EDT
Hmm, the problem also went away by removing "rhgb quiet".
Comment 4 Ray Strode [halfline] 2010-05-12 09:58:58 EDT

*** This bug has been marked as a duplicate of bug 582265 ***
Comment 5 Qian Cai 2010-05-12 21:42:23 EDT
The problem is still persistent after upgraded to plymouth-0.8.3-1.el6.
Comment 6 Ray Strode [halfline] 2010-05-12 22:01:24 EDT
Note after upgrading to plymouth-0.8.3-1.el6 you need to rebuild your initrd with /usr/libexec/plymouth/plymouth-update-initrd or by installing a new kernel.

I'm going to close this bug because it really sounds like a bug that's already been fixed.  If after rebuilding your initrd you still have a problem, please reopen.
Comment 7 Qian Cai 2010-05-13 01:55:59 EDT
After running the command, I am getting,
"could not start boot splash: Can not access a needed shared library"
Comment 8 Ray Strode [halfline] 2010-05-13 08:22:01 EDT
That means plymouthd couldn't find a boot splash to load.   This shouldn't happen if your initrd was generated properly.

what's the output of 

/usr/sbin/plymouth-set-default-theme ?

Can you attach your initrd?
Comment 9 Qian Cai 2010-05-14 01:05:06 EDT
> /usr/sbin/plymouth-set-default-theme ?
Comment 10 Qian Cai 2010-05-14 01:08:15 EDT
Created attachment 413944 [details]
Comment 11 Ray Strode [halfline] 2010-05-14 10:47:44 EDT
Turns out my fix wasn't in plymouth-0.8.1-3.el6 after all..fixed package building now...

*** This bug has been marked as a duplicate of bug 590774 ***
Comment 12 Qian Cai 2010-05-22 11:48:56 EDT
Created attachment 415872 [details]

Still have the same problem here using plymouth-0.8.3-3.el6.x86_64 + 2.6.32-28.el6 kernel.
Comment 13 Qian Cai 2010-05-22 15:40:25 EDT
After fully updated the system, it went away.

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