hello DRC, yes, I know you are the only one. Many thanks for all the support you provide to us!
I apologize for forgetting about the reply in the other thread. Regarding systemd-run --scope --user /opt/TurboVNC/bin/vncserver -wm mate :1 For me (Ubuntu 22.04, Mate desktop, turbovnc 3.1.1) this makes the (physical) session crash on logout! Due to this and other bugs in systemd & co (maybe even with TVNC?), my supervisor and I decided to drop systemd-logind suspend and just use manual suspend. > I will experiment with the workaround and see how it changes the observations. > Please be patient, as I am working on about five things at once. Sorry for the workload I imposed on you. I will revisit this once we move to Ubuntu 24 or even 26. For the record: A workaround using tmux works (with basic testing): Create (user) cron job: @reboot /usr/bin/tmux new-session -d -s vnc /bin/bash then when logged in via ssh, connect to tmux:vnc and start TVNC from there, and detach from tmux. This avoids the blocking ssh session. Needless to say, this is a hack. 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 visit https://groups.google.com/d/msgid/turbovnc-users/CAPBq%2Bwae3Y1FCdN%3Dqko4O%3Df0_%2BaWCCo4kdgYLJP250W4KyXaew%40mail.gmail.com.
