Bug 1602855

Summary:	gray screen and high cpu usage with vncviewer in fullscreen mode
Product:	Red Hat Enterprise Linux 7	Reporter:	Tomas Hudziec <thudziec>
Component:	tigervnc	Assignee:	Jan Grulich <jgrulich>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.6	CC:	tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	tigervnc-1.8.0-8.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-30 08:02:40 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-18 16:15:57 UTC

Description of problem:
gray screen with vncviewer in fullscreen mode and high cpu usage of vncviewer

Version-Release number of selected component (if applicable):
tigervnc-1.8.0-7.el7.x86_64
gnome-session-3.28.1-3.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. $ vncserver :1
2. $ vncviewer -FullScreen :1

Actual results:
gray screen is present

Expected results:
correct vnc desktop should be shown

Additional info:
probably caused by gnome-session update
non-fullscreen mode works fine

Comment 2 Jan Grulich 2018-07-19 05:56:02 UTC

This seems to be this https://github.com/TigerVNC/tigervnc/issues/660 upstream issue. I'll backport fix for this to RHEL 7.6.

Comment 3 Jan Grulich 2018-07-19 07:31:01 UTC

Fixed with tigervnc-1.8.0-8.el7.

Comment 5 Tomas Hudziec 2018-07-20 14:16:35 UTC

With tigervnc-1.8.0-8.el7 now fullscreen mode of vncviewer works fine, correct VNC desktop is shown. Switching to verified.

Comment 7 errata-xmlrpc 2018-10-30 08:02:40 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