Bug 1343899

Summary:	Disabling vncconfig window
Product:	Red Hat Enterprise Linux 7	Reporter:	Ajinkya Patil <ajipatil>
Component:	tigervnc	Assignee:	Jan Grulich <jgrulich>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	jkoten, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 20:50:05 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:
Bug Depends On:
Bug Blocks:	1393395

Description Ajinkya Patil 2016-06-08 09:23:53 UTC

Description of problem:
While accessing the system remotely using vnc session, a window appears with clipboard options (vncconfig window). How to disable it permanently? 

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


How reproducible:
Always.

Steps to Reproduce:
1.Configure vnc. 
2.Access vnc server remotely .
3.window appears with clipoboard options.

Actual results:
window appears with clipoboard options

Expected results:
Wndow shall not appear.

Additional info:
This window is generated by "vncconfig -iconic" option in /usr/bin/vncserver.
If we edit /usr/bin/vncserver file as follow:-

Before:-
system($exedir."vncconfig -iconic >> " . &quotedString($desktopLog) . " 2>&1 &")

After:-
system($exedir."vncconfig -nowin >> " . &quotedString($desktopLog) . " 2>&1 &")
Window shall not appear but customer wants a command line parameter which works here to disable -iconic option.

Comment 1 Jan Grulich 2016-06-08 11:49:45 UTC

Shouldn't be a problem, it's just that vncserver is a convenient script so you don't need to use Xvnc directly. I would still recommend to the customer to use Xvnc directly when they need specific usage, but it's not a big deal.

Comment 8 errata-xmlrpc 2017-08-01 20:50: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/RHSA-2017:2000