Forum Replies Created
-
Posts
-
Hello, the log actually shows 10 events Ctrl+LeftClick where you issued 5 left and 5 right button clicks. It looks that events are created with wrong button code. We managed to reproduce, so I think we are going to open a Trouble Report.
Do you manage to run a terminal in the remote session and type the command
setxkbmap fr? Does it change something?Hello, xev reports correct events and keymap looks OK as well.
For example, qwerty produces events keypress/keyrelease for Q W E R T Y. I can’t see the E becoming 9.
Enter and Backspace are in the expected place in the keymap.Did you run terminal and Xev in the remote session?
Hello. I would expect to find ButtonPress/ButtonRelease events, but I can’t see any.
I had to spend some more words about the way xev works, sorry. In order to record events, you have to generate them on the xev window: move the pointer over the xev window, then Ctrl+click on it.I don’t know if it is possible to setup Xorg to be fully functional with lid closed. Let me suggest to compare the Xorg log in the two cases: started with lid closed and with lid open.
Hello.
Does it makes any different if you use a different client machine with a different OS, Windows for example?
Inspect events forwarded on actions Ctrl+Left Button and Ctrl+Right Button. Launch the xev tool using a terminal in the remote session. You would restrict inspection to mouse and keyboard events for better readability:
xev -event keyboard -event mouseBlack Xorg screen make me think KDE failed to find connected physical screens. Let me suggest to look at KDE log as first thing (try:
journalctl -b -0 | grep -i -E "kde|plasma"). Then look at NoMachine logs (specially search for files$HOME/.nx/*/session).VNC display has such keyboard mapping. Is it possible you are running Xvnc in place of Xorg? Check with command:
ps -C X,Xorg,Xvnc -fHello johngalt17.
Those logs are insufficient to determine the nature of the problem. Please run the interface to change settings on your server, select “Player settings”, “Security”: in that pane check the box “Don’t delete log files on exit”.
Then reproduce the problem, collect the complete log on the server by command
sudo /etc/NX/nxserver --debug --collect.Hello. Would you try to setup keyboard with the “mac” variant? Run a terminl window and issue the command
setxkbmap -layout se -variant mac.Hello, we inspected logs you sent but we didn’t find any error. Be sure log files are not cleaned up: on server side, run NoMachine Player settings, go to “Player settings”, “Folders”, “Security” then check box “Don’t delete log files on exit”.
Hello. The keyboard layout of the client is irrelevant. You need to take care of the keyboard layout on the remote server host. NoMachine forwards keyboard events as “raw keys” (physical key codes, the symbol impressed on the keys don’t matter), so the remote server layout is the one that really matters. NoMachine does not provide any tool for changing keyboard layout as you can use the remote host system settings to change it accordingly to your needs.