On 11/5/18 11:59 AM, Torsten Kupke wrote:
> My Question is: Where do I have to place this command so that it takes
> effect when activating the tvnc session both on the local screen and
> from remote? Is it needed by the tvnc server or only by the tvnc viewer?
> Perhaps you remember on my host the tvnc server is automatically started
> at boot time (see threat "Is it possible to start vncserver
> automatically at boot time?"). Here are some candidates I know:
TVNC_WM will only control the window manager in the TurboVNC session,
not the "local" display on the TurboVNC host.
> /etc/sysconfig/tvncservers
> /etc/init.d/tvncserver?
> /opt/TurboVNC/bin/vncserver
> ~/.vnc/xstartup.turbovnc
Oops. Yes, that was a legitimate oversight on my part. I've added a
new option to vncserver (-wm) that allows TVNC_WM to be set from the
command line. You should now be able to add that option to the
VNCSERVERARGS[] array in your tvncservers file, using the latest 2.2.x
stable pre-release build from:
https://turbovnc.org/DeveloperInfo/PreReleases
NOTE: only the server is needed from the pre-release build. You can
still use the 2.2 viewer.
Let me know if it works. You can also now specify the equivalent of
TVNC_WM in /etc/turbovncserver.conf (system-wide) or
~/.vnc/turbovncserver.conf (per-user.)
I'm going to look into a better way of deploying xstartup.turbovnc in
the next major release.