This is quite an edge case, and is only seen on Chrome-based browsers on Android 13 (I tested Chrome and Edge). It is only seen at the first login. For me, on this first login I had to bypass the warning about "Your connection is not private" and resend my login details. When this bug is triggered, it is not possible to type in the ThinLinc session with the physical keyboard - the input does not seem to be recorded at all. To reproduce this bug, simply log in to a WebAccess session. If needed, clear your browser history first to simulate this first login. Open the terminal or other application, and note that typing with the physical keyboard inside the session is not possible. To get around this issue, either open the clipboard from the ThinLinc side menu and type something in the textbox there, or simply log out and back in again. It is also possible to open the on-screen keyboard to type in the session, but that does not trigger the physical keyboard to start working. If I do the same reproduction steps on Firefox on Android, the physical keyboard gives input in the session.
Tested again when using a working cert, and could use the physical keyboard without any issues then. Closing this bug.
