You don't have to use the TurboVNC Session Manager. Both the TurboVNC
User's Guide and the "New TurboVNC Connection" dialog itself explain
that, if you enter a TurboVNC host into the "VNC server" field without
specifying a VNC display number, the TurboVNC Viewer will start the
TurboVNC Session Manager for that host. The TurboVNC Session Manager is
a "secure by default" solution, so it uses SSH for encryption and
authenticates using a one-time password passed through the SSH tunnel.
If, however, you want to connect directly to a TurboVNC session without
using the TurboVNC Session Manager, then you have to specify the VNC
display number (e.g. localhost:1 or localhost:0). TurboVNC 2.2.x and
prior (and other VNC solutions, such as TigerVNC) assume Display :0 if
the VNC display number isn't specified, but TurboVNC 3.0.x and later
assume that you want to use the TurboVNC Session Manager if the VNC
display number isn't specified.
As to why the TurboVNC Session Manager is failing, Ubuntu 22.04 and
other modern Linux distributions use X Display :1 for the primary X
server (which is often Xwayland running on top of a Wayland session)
after you log in locally. Apparently something happened that caused
/tmp/.X11-unix/X1 to be deleted, so the vncserver script didn't know
that the primary X server was using Display :1, and it tried to use that
display number itself. Xvnc didn't actually start, because the Unix
domain socket for Display :1 was already bound, and
/opt/TurboVNC/bin/vncpasswd erroneously tried to obtain an OTP from the
primary X server. I think the correct way to fix that is to modify
vncserver so that it tries to listen on a Unix domain socket for a
particular display number before assuming that the display number is
available. (Referring to https://github.com/TurboVNC/turbovnc/pull/42,
another user tried to get me to integrate a similar patch years ago, but
the issue they were experiencing was a lot more esoteric, and I could
never reproduce it.) In the meantime, however, you should be able to
work around that issue by logging out and back in again, which should
restore /tmp/.X11-unix/X1. After /tmp/.X11-unix/X1 is restored, the
TurboVNC Server will choose Display :2 for the TurboVNC session.
As far as why the VNC desktop was overlaid on the native desktop, that
could have also been related to the aforementioned problem. When Xvnc
failed, the vncserver script still tried to start the window manager.
(I need to examine why Xvnc didn't return an error code that caused the
vncserver script to abort.) Since the vncserver script creates a unique
DBus instance, perhaps the window manager you are using was able to
install two copies of itself on the same display.
Anyhow, I have a couple of legitimate issues to look into, but hopefully
that gives you enough information to work around the issues.
DRC
On 12/19/23 6:42 AM, tkans...@t-online.de wrote:
Hi,
yesterday I upgraded my Ubuntu workstation from version 18.04 via
20.04 to 22.04. Firstly I proceeded using the TVNC server 2.2.7, and
detected, when locally connecting to the running TVNC session, that
its desktop was transparently overlayed over the native desktop. Of
course, the viewer window also was displayed showing its toolbar and
the usual desktop content. Today I installed TVNC 3.1 replacing TVNC
2.2.7.Now, when I try to connect locally (viewer and server running on
the same machine), firstly I get the expected window "New TurboVNC
Connection" displaying the local hostname in the VNC server field.
When clicking connect, I get the window "SSH Password for <MY
USERNAME>@<WORKSTATION NAME>" (with the real names) showing my
username in the appropriate field. When entering my password, I get
the next expected window "TurboVNC Session Manager" showing the X
display name of the (obviously already running) TVNC session
<WORKSTATION NAME>:1 nearby the buttons "Connect", "New OTP",
"View-only" and "Kill". When clicking "Connect" I get the attached
error message. What can I do to fix this? Is it really necessary to
use a one-time password? Or can I simply use my own normal password as
before?
BR
tkansgar
--
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/1702986179015.1374600.9e23d95d935780794dc2db9af331b3d4f54e88a2%40spica.telekom.de
<https://groups.google.com/d/msgid/turbovnc-users/1702986179015.1374600.9e23d95d935780794dc2db9af331b3d4f54e88a2%40spica.telekom.de?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/c0c302de-0371-092f-5a8d-6db5882d8754%40virtualgl.org.
