Wrong keyboard mapping in Linux

Hello

What is your Linux system? Is it Ubuntu?

Can you share with me the output of `setxkbmap -query`?

Thanks very much,

Hi Richard,

I did this test with Ubuntu 18.04.2 LTS and with Debian. In both cases the problem appears.

Here you have the output:

rules: evdev
model: pc105
layout: es,us
variante: ,

Thank you!

Hello,

Thanks for confirming your setup, I wanted to make sure I was trying this in the same environment as you.

Can you try switching your keyboard layout in Windows to `US Keyboard` (leaving your remote Linux system in the Spanish layout), and let me know if that fixes the issue?

Thanks again,

Hi Richard,

I have changed the keyboard layout in my Windows 10 to US Keyboard and now it works perfectly.


The problem is that I can't have the keyboard changed to US because I need the keyboard in Spanish, how you can imagine.

Can you do a fix to solve this bug?

Thanks!

Hello

Thanks for confirming that changing to US keyboard layout works around the issue. I do understand that it's not a proper solution.

Unfortunately, it is not a quick fix for us to resolve this. I have created an issue to track this internally and will post back here once we have a resolution, but right now I can't say when that will be.

To explain a little bit why this is a complicated problem:

When you press a key on the keyboard, the OS translates this button press into a key code. Every platform has its own different set of keycodes (and Linux has a divergent set of keycodes again, depending on the specific input driver). Because keycodes are not consistent across platforms, we must translate the key code into a platform independent value, and then reverse that translation at the other side.

Given the different possible combinations of platform keycodes, keyboard hardware, and hard-and-soft keyboard layouts, you might understand why this process is tricky to get exactly correct!

As I said, I will post back here when I have an update on this. In the meantime if you have further questions or issues please don't hesitate to ask!

Thanks again,

Hi Richard,

Thanks for the info.


I will wait for the solution.

Best regards,
Jose

Hello

I realize this is an old post, and thank you for your patience. The latest Wayk Now (2020.2.0) contains some improvements that may be helpful.

When you have a session open, you can enable the option "Send Input as Unicode" from the session menu (that can be toggled quickly with the keyboard shortcut [Ctrl]+[Shift]+T - [Command]+[Shift]+T on macOS). With this option enabled, Wayk Now will send the actual characters you type to the remote machine instead of key codes, so regardless of the keyboard layouts and input language on either computer you should see exactly what you typed. This should even work with when entering complex unicode characters directly (for example, when using unicode composition on Linux).

At this point, I'd consider the feature to be experimental and I'll encourage you to try it out and give feedback and questions. Please note that as well as requiring the latest Wayk Now client on the machine you are connecting from (2020.2.0), a relatively recent Wayk Now version is also required on the server (2020.1.6 or newer).

Thanks and kind regards,