Bug 1605325

Summary: vncviewer holds focus of whole screen after exiting fullscreen mode
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Hudziec <thudziec>
Component: tigervncAssignee: Jan Grulich <jgrulich>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.6CC: amike, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 08:03:01 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 Tomas Hudziec 2018-07-20 14:52:52 UTC 
Description of problem:
Focus of vncviewer remains on whole screen after exiting fullscreen mode.

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

How reproducible:
95%

Steps to Reproduce:
1. start vnc server:
   $ vncserver :1
2. connect to it with vnc viewer in fullscreen mode:
   $ vncviewer -FullScreen :1
3. press F8 to open the context menu
4. click on "Full screen" in context menu to exit fullscreen mode
5. click somewhere outside the vncviewer window to lose focus from it

Actual results:
It is not possible lose focus of the vncviewer window, it still catches all mouse clicks and key presses from whole screen.

Expected results:
It should be possible to lose focus of the vncviewer window, e.g. to switch to another application, minimize, or move the window.
Comment 2 Jan Grulich 2018-07-23 09:14:26 UTC 
Should be fixed with tigervnc-1.8.0-9.el7.
Comment 4 Tomas Hudziec 2018-07-30 10:34:09 UTC 
It is fixed in tigervnc-1.8.0-9.el7, not able to reproduce now. Switching to verified.
Comment 5 Jan Grulich 2018-08-30 05:26:34 UTC 
*** Bug 1623699 has been marked as a duplicate of this bug. ***
Comment 7 errata-xmlrpc 2018-10-30 08:03:01 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-2018:3059