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 1664801 - vncviewer in full screen holds keyboard and mouse after moving off the monitor on a two screen configuration with FullScreenSystemKeys on
Summary: vncviewer in full screen holds keyboard and mouse after moving off the monito...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tigervnc
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-09 16:59 UTC by Morgan Rowley
Modified: 2019-11-01 20:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 12:43:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2081 0 None None None 2019-08-06 12:43:10 UTC

Description Morgan Rowley 2019-01-09 16:59:28 UTC
Description of problem: When vncviewer is opened in fullscreen on one screen in a two screen configuration with FullScreenSystemKeys on all mouse clicks and key presses are still captured by vncviewer. With FullScreenSystemKeys off there is no problem.


Version-Release number of selected component (if applicable):
tigervnc-1.8.0-13.el7

How reproducible:
Consistently

Steps to Reproduce:
1.In a two screen configuration launch vncview in fullscreen mode with FullScreenSystemKeys on (the default)
2. Ensure the mouse is clicked in the vncviewer screen.
3. Move the mouse over to the screen vncview is not on and attempt to click
4. With the mouse still over on the other screen attempt to type on keyboard.

Actual results:
Mouse clicks and key presses are still sent to the vncviewer screen.

Expected results:
Mouse clicks and key presses are sent to the screen without vncviewer.

Additional info:
Performing the same steps with FullScreenSystemKeys off does not reproduce the issue.

Comment 5 Jan Grulich 2019-02-28 18:45:15 UTC
Fixed with tigervnc-1.8.0-17.el7.

Comment 10 Bill Sanford 2019-05-14 16:15:07 UTC
Tested and verified with RHEL-7.7-20190514.0 & tigervnc-1.8.0-17.el7.

Comment 12 errata-xmlrpc 2019-08-06 12:43:05 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/RHBA-2019:2081


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