Dear turbovnc experts, if I start a (turbo-)vnc server and then log out the physical session, the VNC session is terminated as well (or broken). I think this is a limitation of (turbo-)vnc? It does work with CentOS7.
In order to work around this, I create the (turbo-)vnc server in a (localhost) ssh session to the target host (is there a better solution?) ;-) This hack seems to work (I can still use the VNC session even if the physical session is logged out). However, it seems that in this specific situation, when locking a vnc session (automatic or manual), the login manager does not accept my password for unlocking the session (it is stuck). I cannot unlock the session by running "loginctl unlock-session" from an ssh connection. I am using TurboVNC 3.1 on Ubuntu22.04 (Standard GNOME with gdm3). I am using virtualgl so WaylandEnable=false is set in /etc/gdm3/custom.conf. Is it true that logging out of the physical session (where the VNC session was created) is not supported at all (on Ubuntu22)? Many Thanks and Best Regards! Felix -- 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/22506e22-5e4f-455e-92fd-973019316e59n%40googlegroups.com.
