graywolf

[graywolf]

NoMachine does not try to change keyboard layout. Such problem occurs because display server didn’t initialize the virtual keyboard device (it does not depend on NoMachine). Setting layout in KDE should be enough to fix the problem permanently.

[graywolf]

Hello, I’m considering creating a Feature Request to get NoMachine client handle volume keys.

[graywolf]

Hello. Try to change keyboard layout to PL in KDE settings on the remote host.

You could also setup using the command line. Run a terminal on the remote desktop and type the command setxkbmap pl.

[graywolf]

OK, I was able to replicate on my own. It looks a different problem, so a new TR is appropriate: The Win key gets stuck when used in shortcuts

[graywolf]

Hello, this seems like a known problem:

Some key combinations are not captured on Windows when the grabbing of the keyboard is enabled

[graywolf]

Go into Cinammon system settings pane and check for keyboard layout: add German layout if needed.

[graywolf]

Thank you for letting me know.

[graywolf]

Nothing unusual in the keymap.

Host is Win10, remote is Ubuntu 16.04

Please, confirm the setup is like the following:

• Client (local to the user): Windows 10
• Server (remote to the user) Ubuntu

and gather client and server logs: How to gather debug logs for support requests

Then send logs to: forum (at) nomachine (dot) com

 

[graywolf]

Hello.

I have not found anything useful in logs. Would you try the latest NoMachine software update (6.12.3)?

[graywolf]

xkbcomp.out has been rejected. Please try xkbcomp.txt.

[graywolf]

Would you run this command on the remote Ubuntu host:

xkbcomp -xkb $DISPLAY - > xkbcomp.out

and let me see the file xkbcomp.out?

[graywolf]

Hello.
I think you encountered the issue described in this topic: Some issue with Keyboard mapping

and here: Keyboard layout is wrong when sharing a physical desktop which explains that it is not a NoMachine issue.

[graywolf]

Hello. Do you still experience that problem?

Btw, provided Xterm is installed, console custom session must just work. Otherwise something has gone bad on your system or in NoMachine installation and errors would have been recorded in nxserver.log and /usr/NX/var/log/node/.

[graywolf]

Isn’t xterm installed? That could be the reason console session didn’t work.
Look at errors nxserver.log: there are recorded the unexpected terminations or relevant processes and missing xterm problem.

[graywolf]

take a look of unity7.log and unity7.log.*.gz about the date and time you got the problem.

Try also this: run a custom NoMachine session with only xterm into it. Use xterm to test the Unity support with command /usr/lib/nux/unity_support_test -p.

[Author]

Posts