hi DRC, I just managed to reproduce it with TVNC 3.1.1-20240118:
- Ubuntu22.04 with GDM3 and GNOME3(x11) session - installed ubuntu-mate-desktop, dbus-x11 - installed some other packages - "vncserver" (without arguments) took :2 because :1 had a /tmp/.X11-unix/X1 owned by root - the vnc session is created successfully - connect to hostname:2 from a TVNC 3.1.1 client: OK - log out of the local GNOME3 session - the VNC Session (:2) disconnects after a short while - nothing suspicious in (server) log file > Does it also occur if the TurboVNC session is started independently, e.g. from an SSH session? No, then I get a different error: the vnc session cannot be unlocked after a lock. WaylandEnable=false is set. Many Thanks and Best Regards! Felix DRC schrieb am Donnerstag, 18. Januar 2024 um 21:30:12 UTC+1: I still can't reproduce it. Does the issue occur only if the TurboVNC session is started from the local session? Does it also occur if the TurboVNC session is started independently, e.g. from an SSH session? I'm suspicious because you said "the physical/:0 GNOME3 session." On my system, a local GNOME session uses :1 if WaylandEnable=false (which you said was the case on your system.) That may indicate that something is different about your system. Also, please upgrade the server to the latest 3.1.x pre-release build ( https://turbovnc.org/DeveloperInfo/PreReleases) so that we're on the same page. That build automatically enables '-listen local', so it shouldn't be necessary to specify Display :2 anymore. DRC -- 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/600fa4dd-be47-462b-83a8-1bccd5487ecan%40googlegroups.com.
