TurboVNC 3.1 introduced server-side key mapping, whereby the viewer
sends raw scan codes to the server and the server translates those into
X11 keysyms based on the key map that is active in the TurboVNC
session. Thus, the key map in the TurboVNC session now matters, and the
key map on the client no longer matters. Make sure that the correct key
map is set in the TurboVNC session.
On 1/16/24 3:10 PM, Torsten Kupke wrote:
Hi,
I'm a software developer using Qt Creator under Ubuntu. Since the
recent upgrade to Ubuntu 22.04 and installing TVNC 3.1 I have the
problem, that, when debugging my code with gdb in Qt Creator, that
some keys don't work as usual. For some details see
https://forum.qt.io/topic/153654/some-keys-not-working-properly-in-debug-session!
Now I detected, that this only happens, when working from home (under
Windows 10) using the TVNC client 3.1 (which is Java). When I work
locally on my workstation, also with the Java TVNC client 3.1
connected to the same TVNC server running locally, all keys work as
desired. What could be the reason for this problem, and is it fixable
in any way?
BR
tkansgar
--
You received this message because you are subscribed to the Google Groups "TurboVNC
User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/turbovnc-users/d74ff29d-b24b-737c-052b-11b3a3e2665b%40virtualgl.org.
