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.
Bug 1190768 - Wireless keyboard and mouse do not functions after installing RHEL 7
Summary: Wireless keyboard and mouse do not functions after installing RHEL 7
Keywords:
Status: CLOSED DUPLICATE of bug 1110523
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: xorg-x11-drv-mouse
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Peter Hutterer
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-09 15:41 UTC by Arjay Hinek
Modified: 2015-04-08 23:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-08 23:39:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Arjay Hinek 2015-02-09 15:41:02 UTC
Description of problem:After installing RHEL 7, my wireless mouse and keyboard are mute.  I have checked the receiver and it still has both mouse and keyboard mapped, and I have checked the USB port with a thumb drive, and it is functioning. I have had the Helpdesk on 14 at RDU try on their own RHEL 7 machine, and they see the same problem.


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


How reproducible:constant


Steps to Reproduce:
1.Turn on laptop or unlock
2.turn on on wireless mouse or keyboard
3.try to use mouse or keyboard

Actual results:
No response form mouse or keyboard

Expected results:
cursor should move and key stroke entry should be recognized

Additional info:
I can use my scratch pad, but because my job requires a large amount of presenting and using my wireless mouse to navigate the screen, this is a major problem.

Comment 2 Peter Hutterer 2015-03-25 22:22:39 UTC
What's the model number of the devices?

Do you see the device show up in the kernel? i.e. do you get event nodes for them and if so do those nodes send events at all? evemu-record should show you
http://people.redhat.com/~phuttere/rpms/evemu/

If not, then this is either a kernel or a HW issue - I take it you tried the HW on another system since to make sure the dongle isn't busted?

This bug could also be a dupe of Bug 1110523 which was fixed in kernel-3.10.0-148.el7, if you can give that version a try that'd be much appreciated, thanks.

Comment 3 Arjay Hinek 2015-04-06 11:18:52 UTC
Yes we tried the hw on another system.  Ultimately we determined that the HW would only work with USB2. (I believe that was the "fix" in 3.10.0-148.el7. This bug can be closed.

Comment 4 Peter Hutterer 2015-04-08 23:39:58 UTC
Ok, thanks for re-checking, I'm closing this as duplicate of the other bug then.

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


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