RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Unable to type the letter 'p' (not joking)


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

RHEL6 nightly build as of 7/24

How reproducible:

100%

Steps to Reproduce:
1. Try to tye the letter 
2.
3.
  
Actual results:

Try to tye the letter 

Expected results:

Able to type the letter 'p'

Additional info:

I booted to an F13 livecd and was able to use the letter p so it is not a hardware problem. FYI, every time I used p here I had to paste it...

Not sure what to file this under.

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

And of course after a fourth reboot prior to which I updated the following I am able to type pppppppppppppppppppp... I'm not crazy, really...

selinux-policy-3.7.19-34.el6.noarch
libcollection-0.5.0-21.el6.i686
libini_config-0.5.1-21.el6.i686
libudev-147-2.22.el6.i686
xulrunner-1.9.2.8-1.el6.i686
libdhash-0.4.0-21.el6.i686
sssd-client-1.2.1-21.el6.i686
sssd-1.2.1-21.el6.i686
libgudev1-147-2.22.el6.i686
udev-147-2.22.el6.i686
gnome-settings-daemon-2.28.2-10.el6.i686
module-init-tools-3.9-16.el6.i686
firefox-3.6.8-1.el6.i686
selinux-policy-targeted-3.7.19-34.el6.noarch

- James

*** This bug has been marked as a duplicate of bug 595763 ***