Bug 1623699

Summary: tigervnc will not give up focus on fullscreen mode with multiple monitors
Product: Red Hat Enterprise Linux 7 Reporter: Andrew Mike <amike>
Component: tigervncAssignee: Jan Grulich <jgrulich>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: alanm, jwright, mkolbas
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-30 05:26:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrew Mike 2018-08-29 22:28:39 UTC 
Description of problem: While in fullscreen mode on one monitor, the TigerVNC client will not give up focus to a window on another monitor if that window is clicked in.

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

How reproducible: Consistently.

Steps to Reproduce:
1. Start the TigerVNC client and move to Monitor 1.
2. Start another application and move to Monitor 2.
3. Using the TigerVNC client, connect to a VNC server.
4. Click off to the application on Monitor 2, then click back. Notice how the focus was switched.
5. On TigerVNC, press F8 and select "Full Screen" in the context menu.
6. Move the mouse cursor from the TigerVNC window and click on the window on Monitor 2.

Actual results:
Focus is not shifted to the application on Monitor 2, and no keyboard or mouse input is passed to said application.

Expected results:
Focus is shifted to the application on Monitor 2, and mouse and keyboard input is passed as normal.

Additional info: Upstream bug is https://github.com/TigerVNC/tigervnc/issues/447, with a patch at https://github.com/TigerVNC/tigervnc/commit/7e546febadb6e6cc66138c2316c8c19ca8aab2b1.
Comment 2 Jan Grulich 2018-08-30 05:26:34 UTC 

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