Bug 715041 - 5 key triggering multilple keys
Summary: 5 key triggering multilple keys
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: distribution
Version: 5.8
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: RHEL Program Management
QA Contact: Ondrej Hudlicky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-21 17:16 UTC by mike
Modified: 2016-09-19 16:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:03:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description mike 2011-06-21 17:16:10 UTC 
Description of problem:
When i hit the 5 or t key it hits multiple keys.

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

How reproducible:
Almost every time i hit the key.

Steps to Reproduce:
1.Tap the 5 key on a macbook
2.
3.
  
Actual results:
25112525125131253251251

That was me hitting the 5 key.
Expected results:
5555555


Additional info:
tested hardware on another distro and the keyboard worked fine.
Comment 1 RHEL Program Management 2014-03-07 12:40:08 UTC 
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 2 RHEL Program Management 2014-06-02 13:03:11 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Comment 3 mike 2016-09-19 16:31:29 UTC 
ok
Note You need to log in before you can comment on or make changes to this bug.