Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1343899 - Disabling vncconfig window
Summary: Disabling vncconfig window
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tigervnc
Version: 7.2
Hardware: Unspecified
OS: Linux
Target Milestone: rc
: ---
Assignee: Jan Grulich
QA Contact: Desktop QE
Depends On:
Blocks: 1393395
TreeView+ depends on / blocked
Reported: 2016-06-08 09:23 UTC by Ajinkya Patil
Modified: 2020-09-10 09:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-01 20:50:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2000 0 normal SHIPPED_LIVE Moderate: tigervnc and fltk security, bug fix, and enhancement update 2017-08-01 18:33:08 UTC

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:

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:-

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

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.


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