If something goes wrong during the VNC authentication phase, then the client will show an error string in English and not in the configured local language. The problem is that the VNC protocol sends error strings rather than error codes in this case (see SecurityResult in the spec.). Historically these were rare so not much of an issue. However with bug 37 fixed these are more common as some shadowing errors will use this mechanism. Possible fixes: - Translate the strings on the client. This should work well for us since it is a known server and therefore known strings. It is not a particularly good solution for upstream though. - Improve the protocol to send more error codes. There is a 32-bit field available so there is definitely space. We just need to coordinate things with other VNC implementations.
