Re: [TurboVNC-Users] Issue with Arch's Linux AUR

Oh, nice, thanks, will add that to AUR. On Tuesday 27 February 2024 at 18:29:57 UTC+1 DRC wrote: > Ah, OK, so it actually is using TurboVNC on the server, but TurboVNC is > installed under /usr rather than under /opt/TurboVNC. In that case, you > don't even need to do the symlinking. You can

Re: [TurboVNC-Users] Issue with Arch's Linux AUR

Ah, OK, so it actually is using TurboVNC on the server, but TurboVNC is installed under /usr rather than under /opt/TurboVNC.  In that case, you don't even need to do the symlinking.  You can just set TVNC_SERVERDIR=/usr in the environment on the client prior to invoking the TurboVNC Viewer.

Re: [TurboVNC-Users] Issue with Arch's Linux AUR

Thank you for the reply. I started it again with `-loglevel 110`, and the client didn't show anything obvious but noticed in the server log file `sh: line 1: /opt/TurboVNC/bin/xstartup.turbovnc: No such file or directory`. This solved the issue: `sudo ln -s /usr/bin/xstartup.turbovnc /opt/Turb

Re: [TurboVNC-Users] Issue with Arch's Linux AUR

The TurboVNC Viewer has two modes of operation. When you pass only a hostname or IP address to the TurboVNC Viewer, it tries to use the TurboVNC Session Manager.  The TurboVNC Session Manager connects to the TurboVNC host using the viewer's built-in SSH client and obtains a list of all TurboVN

[TurboVNC-Users] Issue with Arch's Linux AUR

I'm looking for any hints that might help resolve the problems we see when using TurboVNC in Arch/Manjaro. This is how far I managed to investigate (comment in AUR ): Trying `vncviewer my_ssh_config_host` I got `Could not execute /opt/