If you do upgrade to TigerVNC, however, please note the following issue: Using it, I was able to get clipboard sharing working (via the previously mentioned vncconfig command). Īs an alternative, I would suggest using the TigerVNC server, which is included in my Debian installation and is probably available for many other distros as well. Unfortunately, the current version is no longer open source and requires a commercial license. It's also worth noting that the official TightVNC web site says that this version (1.3) is outdated and not supported. At least the version I have ( tightvncserver version 1.3.9-9+deb10u1, from Debian 10) doesn't. It appears that the TightVNC server package doesn't have this support. (click on Options) then make sure that Disable clipboard transfer is not checked. This option is accessible when you launch TightVNC.
Using TightVNCon Windows, make sure that the option Disable clipboard transfer is not checked. Note: The DISPLAY environment variable or the -display option will be used to identify the display/window in which to be active. The -nowin flag can be used if you always want clipboard support but don't wish to clutter the desktop with this windowĪlternatively the -iconic option can be used to make it iconified by default. The vncconfig command puts up a window with some checkboxes which can be used to disable clipboard transfers if required. Note that without a running instance of vncconfig there will be no clipboard support.
Its main purpose when run in this mode is to support clipboard transfer to and from the VNC viewer(s). When run with no options, it runs as a kind of "helper" application for Xvnc. Note that it cannot be used to control VNC servers prior to version 4. Vncconfig is used to configure and control a running instance of Xvnc, or any other X server with the VNC extension. With the unlikely name of vncconfig on Linux, you can get bidirectional cutbuffer/clipboard interaction.
0 kommentar(er)
