Forum / NoMachine for Windows / Some issue with Keyboard mapping
- This topic has 6 replies, 2 voices, and was last updated 4 years, 1 month ago by
Tor.
-
AuthorPosts
-
August 3, 2020 at 07:59 #28808
noluke
ParticipantHi everyone,
I’ve just installed NoMachine on my linux machine (as server) and on my Windows 10 machine (as client). I launched NoMachine on Windows to control my linux machine. It works great, but I have some issue with the keyboard mapping. I set the Italian keyboard on Windows, but it seems that a few characters are mapped wrongly. The “/” character, i.g, is on my “-” instead. Most of the Hold-key characters are messed up.
Any way to fix this problem?
Thank you. luke.August 3, 2020 at 11:07 #28827Tor
ParticipantHi Luke. Can you run the command
setxkbmap -print
in a terminal on Linux and let us know the result? Generally such problems are related to the server keyboard layout not matching the physical keyboard you’re using on the client. For example if you’re using an italian keyboard on Windows, select the italian layout on the server so the remote system correctly interprets the pressed keys.August 4, 2020 at 07:15 #28845noluke
Participantsetxkbmap -print
xkb_keymap {
xkb_keycodes { include “evdev+aliases(qwerty)” };
xkb_types { include “complete” };
xkb_compat { include “complete” };
xkb_symbols { include “pc+it+inet(evdev)” };
xkb_geometry { include “pc(pc105)” };
};Thanks
August 5, 2020 at 11:57 #28875Tor
ParticipantHi Luke. Can you confirm whether the command
setxkbmap -model pc105 -layout it
executed in the Linux terminal helps to solve the issue?August 5, 2020 at 14:50 #28878noluke
Participanthi Tor,
Yes, it works.
Actually, I had found such a “Fcitx configuration” tool in my linux machine which did something similar, but the setup get deleted at every startup…just like your command. I would need now to run it automatically at the startup.
ThanksAugust 6, 2020 at 11:31 #28902Tor
ParticipantGreat! We’ve documented this problem here:
https://www.nomachine.com/TR09Q09412
It is due to X.org not setting correctly the keyboard options for the XTEST extension device. Let’s try to work around it.
Create the file.xinitrc
in your home directory (if it doesn’t exist already), and add the following lines (remove the first line if it’s not a new file):#!/bin/sh XTEST_ID=$(xinput list | grep -Eo "Virtual core XTEST keyboard\s*id\=[0-9]{1,2}" | cut -d= -f 2) setxkbmap -device $XTEST_ID -model pc105 -layout it
Run the command
chmod +x .xinitrc
to set executable permissions and run it to verify that it works as expected. Each time your X session will start, the script will be executed and it’ll set correctly your layout.August 6, 2020 at 11:37 #28901noluke
ParticipantOk, I fixed the problem by running the application fcitx on the startup. Thanks
-
AuthorPosts
This topic was marked as solved, you can't post.