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 1728761 - Keyboard and mouse are unresponsive after ~45 days of uptime
Summary: Keyboard and mouse are unresponsive after ~45 days of uptime
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jonas Ådahl
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1766649 1778211 1778212 1778254
TreeView+ depends on / blocked
 
Reported: 2019-07-10 15:44 UTC by jigar
Modified: 2023-12-15 16:37 UTC (History)
15 users (show)

Fixed In Version: mutter-3.28.3-17.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1766649 1778211 1778212 1778254 (view as bug list)
Environment:
Last Closed: 2020-03-31 19:39:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME/mutter/merge_requests/886 0 None None None 2019-10-25 15:37:24 UTC
Red Hat Knowledge Base (Solution) 6091221 0 None None None 2021-06-02 05:03:39 UTC
Red Hat Product Errata RHSA-2020:1021 0 None None None 2020-03-31 19:40:27 UTC

Description jigar 2019-07-10 15:44:26 UTC 
Description of problem: 

On a customer site, there are four servers running with RHEL 7.4. All servers stopped responding on mouse or keyboard inputs after ~45 days of uptime (+/- some days, depending on the server). 

The machines were still running and reachable via SSH. Also the software (server processes) on the machines continued working as expected. Only the desktop did not receive any inputs anymore. However, opening a xterm via SSH on the Desktop worked - although the xterm could not be used, as it did not receive any input from keyboard or mouse.

Removing and re-plugging the keyboard and the mouse directly into the machine, bypassing the KVM switch, did not help.

Version-Release number of selected component (if applicable): 
gnome-shell-3.28.3-8.el7_6
mutter-3.28.3-7.el7_6

How reproducible: Frequently ( with long uptime )

Steps to Reproduce:
1. Keep the system/server up for more than 45 days
2. Check if the keyboard & mouse are responsive
3. If unresponsive, check if it is possible to ssh to the system and work with other software

Actual results: keyboard and mouse become unresponsive

Expected results: Keyboard and mouse should not become unresponsive

Additional info:
1) On some machines, it helped to end the user session and log-in again. Other machines required a reboot.

2) This does not seem to be the Issue 02102030

3) Killing gnome-shell repairs the issue and so does switching runlevels.
Comment 9 Jonas Ådahl 2019-10-29 09:37:33 UTC 
Created attachment 1630072 [details]
timetravel.py

Attaching another tool I've been using. What it does is change the date to 10 minutes before or after the next Xorg timestamp wrap.

The bug reproduces when you go from just after the wrap, to just before, as that jump is large enough to trigger the issue.

E.g. as root, run

./timetravel.py after # jump to just after a timestamp wrap so that timestamps are now relatively small
./timetravel.py before # jump to just before the next timestamp wrap so that timestamps are now relatively large

I could reliably reproduce the issue by running these two commands; it is however possible that it will trigger already after the first, depending on what the timestamp happens to be initially.
Comment 26 errata-xmlrpc 2020-03-31 19:39:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1021
Note You need to log in before you can comment on or make changes to this bug.