![]() ![]() In this version, self-installing executable will not try to install service in Windows Vista. Improved installer and uninstall utility. ![]() Usability improvements in the "New Connection" dialog. vnc files correctly if the first byte of their encrypted representation was zero.įixed problems under Windows Vista where Windows taskbar could remain visible above the full-screen window.įixed a problem with decoding JPEG rectangles wider than 2048 pixels.įixed a bug with not saving log file name correctly on using the Browse button. Also, several other enhancements were made to the code which handles the list of recent connections.įixed a bug with not loading passwords from saved. Now we save unsuccessful connections too so that users would not ever have to re-type server names after connection failures. TightVNC Viewer version 1.3.9 saved only successful connections in the list of recently visited VNC servers. A specially modified VNC server could currupt the heap of the connected viewer causing its crash or malfunction. LastRect, XCursor and RichCursor pseudo-encodings were not properly enabled if they preceded true encodings in the SetEncodings protocol message.įixed integer overflow vulnerabilities reported by Core Security Technologies. Note that -silent should precede other respective options in the command line. That could caused distortions that never updated even with full-screen polling active.Īdded new "-silent" command-line option which modifies the behavior of -install, -reinstall and -remove options and makes them not show informational windows on successful execution. ![]() Disabling file transfers if current user is unknown or nobody is logged in.įixed rendering problems when multiple CopyRects were combined with normal updates. Impersonating currently logged on user while processing file transfer requests. Note that Remotix writes non-debug logs by default so it is required to make them verbose before you reproduce the issue.See the text version from which this document was generated. Note that you need Remotix 6 and higher to get the client app logs. If you found a bug and need to launch Remotix in verbose mode to share the logs with us, here is the how-to. Linux: at /var/log/ (daemon logs) and tmp/ (GUI logs).Windows: in the \Logs subfolder in the Remotix Agent installation folder (service daemon and RC logs) and in %APPDATA%\Remotix Agent (GUI logs).Mac: at /Library/Logs/ (service daemon logs) and ~/Library/Logs/ (agent GUI and RC logs).Remotix Agent logs may be found at the following locations: How to include logs in the reportĪll Remotix desktop apps have a built-in debug mode that allows collecting logs. Please also include the application logs in the report if possible: Remotix logs from the local machine and Remotix Agent logs from the remote one. Note that settings are different for each type of connection: e.g., you need settings for Mac (NEAR) if you were connecting to a Mac with NEAR and Mac (Screen Sharing) if you were connecting with VNC. Please also check the modifier mappings in Remotix Preferences.Which keyboard mode is chosen (Smart or Raw).If you have a question about typing or modifier-related issues, please also mention: Information from the Connection Info window (available from the Remotix Viewer toolbar).If your question relates to the connection speed, please add information about: Version numbers of Remotix and Remotix Agent.Third, please include the following in your mail: Second, please describe what you did, what happened, and what you had expected instead. If you believe that you found a bug, contact us at to make your bug report as informative as possibleįirst, make sure that you are running the latest versions of Remotix and Remotix Agent if possible. Our tech support is always in place to help you get the best experience with Remotix. ![]()
0 Comments
Leave a Reply. |