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 2054507 - Loss control to windows [rhel-7.9.z]
Summary: Loss control to windows [rhel-7.9.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mutter
Version: 7.9
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Jonas Ådahl
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-15 05:40 UTC by Super Tony
Modified: 2022-06-28 09:55 UTC (History)
6 users (show)

Fixed In Version: mutter-3.28.3-31.el7_9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-28 09:54:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-112284 0 None None None 2022-02-15 05:44:52 UTC
Red Hat Knowledge Base (Solution) 6958310 0 None None None 2022-06-01 06:35:06 UTC
Red Hat Product Errata RHBA-2022:5237 0 None None None 2022-06-28 09:54:11 UTC

Description Super Tony 2022-02-15 05:40:11 UTC 
Description of problem:

We have implemented kiosk mode following this documentation - https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/desktop_migration_and_administration_guide/single-application-ode

We have "hover to focus" configuration turned on, and on many occasions we will loose control over the windows after dragging the window around using the super key. We have already applied the latest patches to the OS dated Feb 10, 2022. None of the windows/applications crashed - the mouse cursor just completely loss control over the windows on the desktop. (control via keyboard appears to still work)

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

Mutter is at 3.28.3-30. 

How reproducible:

Started 3 apps - gnome calculator, gnome-terminal, firefox. Start to use super key to drag the windows around. The lock up or freeze up will occur shortly after. When it happens the mouse becomes unusable to the entire desktop, and I can't interact with any windows. When the desktop appears to be frozen, you could regain control by using Alt-F4 to close the last focused window, and once the last focused window is closed, controlling other windows using the mouse cursor starts to work again.

Steps to Reproduce:
1.
2.
3.

Actual results:

We will loose control over windows, and /var/log/messages has the following error logs:

com.redhat.Kiosk.WindowManager.desktop: Window manager warning: Buggly client sent a _NET_ACTIVE_WINDOW message with timestamp of 0 for 0x3e00007 (GNOME Twea)

com.redhat.Kiosk.WindowManager.desktop: Window manager warning: last focus time (1650857183) is greater than comparison timestamp (1650857175).
This most likely represents a buggly client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around…

Expected results:

We expect the ability to fully control all of the windows in KIOSK mode even when using hover to focus function.

Additional info:
Comment 8 Steve Barcomb 2022-04-19 14:01:59 UTC 
Just making a public update to recap the current status since there is work happening that has not been visible.  Tony is the reporter of the bug and he is the customer in the attached support case.  It looks like engineering has identified a possible solution, and Tony is willing to test a scratch build when it becomes available.
Comment 10 Jonas Ådahl 2022-04-25 19:24:23 UTC 
Scratch builds available for download at https://people.redhat.com/~jadahl/rhbz2054507/.
Comment 20 errata-xmlrpc 2022-06-28 09:54:09 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 (mutter bug fix and enhancement update), 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/RHBA-2022:5237
Note You need to log in before you can comment on or make changes to this bug.