There is one application that I use which frequently will crash TurboVNC viewer.
I've attached an image of the error message. Because this error message disconnects the viewer, and a subsequent reconnect immediately has the same problem, my only workaround is to use a different VNC viewer to connect and change the state a bit. Then I can reconnect using TurboVNC. However, the problem will reoccur a few times a day. I am unsure how to create a useful test case for this situation. Is there some kind of debug informational dump that I could do? The application in question is commercial software. Client: Mac OS/X 10.9.5 TurboVNC Viewer 2.0 (20150714) (Java Hotspot 1.6.0_65 x86_64) Server: CentOS 6.4 tigerVNC 1.3.0-16
------------------------------------------------------------------------------
_______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
