TurboVNC 3.1.3 has been released

[DRC]

Binaries, source tarball, and change log are here:
https://github.com/TurboVNC/turbovnc/releases/tag/3.1.3

[Michael Setzer II]

Note if doing update on a remote machine while logged in using turbovnc.

After the update it requires a systemctl daemon-reload to reset the session, or you will not be able to reconnect.

I used

dnf update turbovnc -y; systemctl daemon-reload

That worked for 4 machines, but had one that didn''t restart session, and it required an ssh login and a systemctl reboot to get the machine working.

Think it was that machine had two server sessions of iperf running on two network cards.

But don't want anyone to loose access to remote or headless machines. My machines running Fedora 40 and using xfce, so can't be sure other setups would have similar problems or not.

[DRC]

That would only be the case if you are running the TurboVNC Server as a system daemon, which is supported but is not the default, documented, or recommended way to run it. Your comment is not applicable to the majority of TurboVNC users.

On Nov 8, 2024, at 5:39 PM, Michael Setzer II <mset...@gmail.com> wrote:



--
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 visit https://groups.google.com/d/msgid/turbovnc-users/75a495a2-66b2-4b07-ad98-7e5d782b887bn%40googlegroups.com.