For some reason, Google flagged it as spam, so I had to approve the message. :/
Anyway, if you are connecting to the same machine, you would have to be using the Linux TurboVNC Viewer, which is based on the Java code that is susceptible to the bug in question. Upgrade your TurboVNC package on that machine to 2.2.2, and all should be good. On 4/24/19 5:26 AM, Torsten Kupke wrote: > Sent this today morning already. Don't know, why it was ignored by > Google. Have removed some old mail texts here. > > Hi DRC, > > > in my case the client and the host are the same machine. This way I > locally can work with the same session as from remote. My remote > client is Windows, where I don't use the Java client but the > vncviewer.exe. > > Best regards > > Torsten > > > Am 23.04.2019 um 19:58 schrieb DRC: >> This issue is in the viewer, so you don't need to install anything on >> the host. Just install the pre-release on your client machine. >> >> On 4/23/19 11:53 AM, Torsten Kupke wrote: >>> Very good news! I try to wait for the official release of 2.2.2, >>> since I >>> don't want to install a pre-release on a host of my employer. >>> >>> Many thanks for your work! >>> >>> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/ff17c8c3-3118-3cbc-f3ac-08dc2ab42eac%40virtualgl.org. For more options, visit https://groups.google.com/d/optout.
