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.
On 2/27/24 12:17 PM, terryer wrote:
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/TurboVNC/bin/xstartup.turbovnc`. Now
`vncviewer -sshport 1234 -sshuser myuser hostname` work. Thank you
again for all the support. I'll update the AUR issue.
On Tuesday 27 February 2024 at 17:36:00 UTC+1 DRC wrote:
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 TurboVNC
sessions currently running under your user account on the host.
If no TurboVNC sessions are running, then it starts a new session
and connects to it. Otherwise, the Session Manager presents you
with a list of running sessions, allowing you to choose the
session to which to connect. When connecting to a TurboVNC
session using the TurboVNC Session Manager, the RFB connection is
automatically tunneled through SSH by default, and authentication
is automatically implemented by generating and exchanging a
one-time password with the session through SSH (so effectively you
only have to authenticate with the SSH server.) However, this
mode of operation requires the TurboVNC Server to be installed on
the host, and it expects the TurboVNC Server to be installed under
/opt/TurboVNC by default. It sounds like you have the TigerVNC
Server installed on the host, and the TigerVNC Server isn't
compatible with the TurboVNC Session Manager.
When you pass a hostname or IP address as well as a VNC display
number, TCP post, or Unix domain socket path to the TurboVNC
Viewer, it acts as a regular VNC viewer, connecting directly to
the VNC server listening on the specified interface on the host.
This mode of operation is compatible with the TigerVNC Server and
other VNC servers, but it doesn't have session management
capabilities, nor does it have automatic authentication and SSH
tunneling.
On 2/27/24 3:47 AM, terryer wrote:
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
<https://aur.archlinux.org/packages/turbovnc#comment-958375>):
Trying `vncviewer my_ssh_config_host` I got `Could not execute
/opt/TurboVNC/bin/vncserver -sessionlist, is TurboVNC server
installed in /opt/TurboVNC ?`. And there is no `/opt/TurboVNC`
dir. I started to link the following into a freshly created
`/opt/TurboVNC/bin`: vncserver, Xvnc, vncpassword, webserver. Now
the error remaining is:
```
libjawt.so path: /usr/lib/jvm/java-21-openjdk/lib
Session Manager Error:
Could not execute
/opt/TurboVNC/bin/vncpasswd -o -display :1
on host node1:
The X display ":1" does not support VNC one-time passwords
```
Any hint welcome.
Thanks
--
You received this message because you are subscribed to the
Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/turbovnc-users/b25d079e-6244-4b3e-a08e-7ab9c48ed2een%40googlegroups.com
<https://groups.google.com/d/msgid/turbovnc-users/b25d079e-6244-4b3e-a08e-7ab9c48ed2een%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to turbovnc-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/turbovnc-users/d5eb4426-0971-4b43-b4a5-0072c3d1bbdcn%40googlegroups.com
<https://groups.google.com/d/msgid/turbovnc-users/d5eb4426-0971-4b43-b4a5-0072c3d1bbdcn%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "TurboVNC
User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to turbovnc-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/turbovnc-users/4dc84279-172f-4a97-81c5-5cb9434eacb4%40virtualgl.org.
