Fixed issues

Application launches could hang or time out when smart card authentication was enabled. This issue occurred when the ctxscardsd service restarted while sessions were active, causing the service to lose session information recorded only at session creation.

On machines hosted in Microsoft Azure, session launches could fail intermittently after updating a machine catalog or creating a new one. This occurred because Xorg sometimes required longer than the fixed 30-second startup period to become ready. The Xorg startup wait is now configurable through the WaitXMaxTimeOut Thinwire setting, with a default value of 30 seconds.

After a reconnection attempt was interrupted, for example, by closing the logon window, sessions that used smart card authentication could not be recovered. Subsequent reconnection attempts displayed a gray screen. The session could only be released by manually terminating VDA processes.

When a client's network connection drops and then reconnects using Auto Client Reconnect (ACR), Linux VDA sessions might crash or log off unexpectedly.

When using the Korean server-side IME, the Hangul key and the Hangul/Hanja key did not function.

When FAS was used for session authentication, in-session smart card operations could be very slow or unresponsive. Client certificate authentication and page loads could take several minutes to complete because card polling stalled repeatedly.

Sessions could fail to reconnect, displaying a graphics error followed by a WINSTATION_BUSY error, and requiring the session to be terminated. This occurred when the PostgreSQL configuration database stopped responding, causing the ctxgfx process to block indefinitely.