Disable Composite extension by default in the legacy-friendly TigerVNC build. Justification: Some older versions of Gnome do not work properly when Composite is enabled. This is known to be a problem with RHEL 4 (Gnome 2.8), and it causes the legacy-friendly build to be unusable on that platform. Newer Gnome versions, such as 2.16.0 (the version in RHEL 5), work properly with Composite enabled, but those versions don't support compositing anyhow, so it doesn't matter if we remove the extension. Typically, platforms that are new enough to support compositing are also new enough to not require the legacy-friendly build of TigerVNC. Further, Composite can be re-enabled by simply adding --enable-composite to the XORGCFGFLAGS env. variable prior to executing 'build-xorg build'.
Remove support for building Xvnc against Xorg 7.5. We have fixed the issues that were occurring in the Xorg 7.4 components by upgrading those components. Xorg 7.5 requires autoconf 2.60 and other updated tools that aren't readily available on the legacy platforms we're using with build-xorg (notably: RHEL 4 and 5), and thus no one has successfully built that configuration.
Remove support for building Xvnc against Xorg 7.5. We have fixed the issues that were occurring in the Xorg 7.4 components by upgrading those components. Xorg 7.5 requires autoconf 2.60 and other updated tools that aren't readily available on the legacy platforms we're using with build-xorg (notably: RHEL 4 and 5), and thus no one has successfully built that configuration.
Using build-xorg without -static is not useful, because it causes Xvnc to depend on the dynamic X11 libraries generated by build-xorg in the build directory. Thus, remove -static and make that behavior the default.
Don't pretend that vncserver -fg & works, because closing stdin causes problems with some WM's. Instead, just revert to the original vncserver -fg code and add a separate option for auto-killing Xvnc when run in "background" mode.
Revert default behavior of vncserver (Xvnc will not automatically be killed whenever the WM exits), but also fix vncserver -fg such that it can be successfully backgrounded (vncserver -fg &) to achieve the same effect.
Don't run vncpasswd to create a new VNC password unless one of the VNC auth types is being used with the default VNC password location (~/.vnc/passwd).
Always exit Xvnc whenever the user exits the window manager, and provide a -fg switch to allow Xvnc to run in the foreground (necessary for some grid computing environments)
Clean up the way build-xorg handles GnuTLS. It should now work the same way as configure, allowing GNU_CFLAGS and GNU_LDFLAGS to be overridden on the command line.
[Bugfix] viewers: set server's hostname as a server name. (Thanks to Guillaume Destuynder)
We use the server name for hostname matching in X.509 code. Otherwise
certificate wouldn't match hostname.
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4249 3789f03b-4d11-0410-bbf8-ca57d06f2519
[Bugfix] Handle situation when viewer doesn't send the key release event well.
Happens for example with TightVNC 1.3.10 viewer during following sequence:
"press shift" + "press a" + "release shift" + "release a"
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4237 3789f03b-4d11-0410-bbf8-ca57d06f2519
Sometimes we get copy requests that are partially or fully outside the
framebuffer. Not sure if this is a bug or not, but for now add some handling
to deal with these gracefully.
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4230 3789f03b-4d11-0410-bbf8-ca57d06f2519
[Development] Allow to modify only "desktop", "SendCutText" and "AcceptCutText"
Xvnc's parameters via vncconfig.
Also Xvnc got new option called "-noclipboard" which disables "*CutText"
runtime modification.
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4226 3789f03b-4d11-0410-bbf8-ca57d06f2519
DRC
Adam Tkac
Pierre Ossman