January 23, 2020 at 10:43 #25338
It looks like I’m having this issue https://www.nomachine.com/TR05K02769 between two Ubuntu boxes. One is running 19.10 and the other is running 19.04
Has anyone seen this, and found a fix?
GeraldJanuary 23, 2020 at 16:46 #25347
Yes, gbr, arrow keys don’t work for me either.
The fix that you gave seems pretty complicated. I would have to do quite a bit of research to figure out how to apply it.
It’s a pity that the issue there is marked as “closed”.
I am running the version installed from nomachine_6.9.2_1_x86_64.tar.gz
My machine reports itself as
Linux JimH15 5.3.0-26-generic #28~18.04.1-Ubuntu SMP Wed Dec 18 16:40:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
and I am connecting to reports as
Linux langtran 4.15.0-74-generic #83~16.04.1-Ubuntu SMP Wed Dec 18 04:55:53 UTC 2019 i686 i686 i686 GNU/Linux
Also, the End key doesn’t work, so probably Home and similar keys don’t work either.
And, by the way, how did you find a way to post a new item to the forum? I can’t find it 🙁
JimJanuary 24, 2020 at 11:01 #25359
hi, what DE is it?
The TR referenced is rather old and concerns version 4, no longer supported. If there is a new bug, we’d need to start a new investigation for the latest NoMachine 6 packages.
We test with as many environments as possible and AFAIK don’t have problems with arrow keys.
Can you check that you have # AgentLegacyKeyboard 0 in the node.cfg. ‘0’ is the default setting (although it would be odd that you have it set at ‘1’).
Enable logs, reproduce and submit them to forum[at]nomachine[dot]com. For safe measure submit both server side and client side logs.
Instructions are here: https://www.nomachine.com/AR10K00697January 24, 2020 at 14:39 #25360
I’m runnining XFCE (Xubuntu) on both desktops.
I do have #AgentLegacyKeyboard 0 in /usr/NX/etc/node.cfg
I will activate the logs and submit them early next week.
GeraldJanuary 24, 2020 at 16:18 #25371
Ok, please make sure you reference the title of your topic in the subject of your email 🙂January 27, 2020 at 08:45 #25379
Gerald, the #AgentLegacyKeyboard 0 that you list still has the “#” key before it, which usually means that it is commented out, and therefore having no effect.
Would you like to try removing the “#” character in that control file?
Then make NoMachine on your client exit and start it again, and see if that makes a difference.
JimJanuary 27, 2020 at 11:17 #25385
The default is set to ‘0’. If you wanted to change it and set it to ‘1’ (but I doubt it would change anything because this key was inserted to mitigate a problem coming from old packages), then you would need to remove the #.
@JimH24, the logs you sent didn’t show anything strange. Do this instead: from inside the NoMachine session, open a terminal and execute this command:
xev -event keyboard
then press the not working keys and copy the output you get in the terminal. Paste it here or submit a screenshot.January 27, 2020 at 19:47 #25389graywolfModerator
open a terminal and execute this command
Please, would you run also these, both in remote session as well as on client host:
xkbcomp -xkb $DISPLAY - > xkbcomp.out 2> xkbcomp.err
xprop -root | grep XKB > xprop.out 2> xprop.err
setxkbmap -print > setxkbmap.out 2> setxkbmap.err
and let me look at err, out files?January 28, 2020 at 09:03 #25390
There are probably more keystrokes here than you need — it took me a little while to work out how to click the x to terminate the xev program 🙂 I’m not sure this is all the keys that don’t work, but it might show you what is going on:
Thanks again for looking into this,
Attachments:January 28, 2020 at 09:03 #25391
Thankyou, @graywolf, here are the sizes of the files on disc (from du -h *):
As you can see, the server only produced errors:
server-setxkbmap.err: XKB extension not present on :11.0
server-xkbcomp.err: Error: XKB extension not present on :11.0
Does this mean I should install XKB extension on the server?
I’ll upload the client files that are larger than zero.
JimJanuary 28, 2020 at 10:17 #25401graywolfModerator
XKEYBOARD extension is required to create a proper keymap. Display :11 is unusual, did you do any custom setup of X server?January 29, 2020 at 13:47 #25416
Thanks @graywolf, I don’t remember setting up anything special in the X server. I have a lot of experience with Linux shell scripts, programming in perl etc, but not much with system management. I’ll attach a screenshot of the installed items when I search for “xkeyboard extension” on the server.
The server is a slice of a real computer that we rent from a cloud computing provider.
When I go to connect with NoMachine, today I need to choose amongst the following “Physical displays” on “Ubuntu X server”: 0, 10, 12-17.
I have logged in using number 11, closed processes there and logged out. Now I am going through them, and for each one I’ll log in, close processes running there and log out. When I get to the last one I’ll reboot.
Thanks again for your help,
Attachments:January 30, 2020 at 08:28 #25425
Sorry for not sending logs, as requested. I got sick, and this is my first day back.
Do you still want log files from me?
GeraldJanuary 30, 2020 at 08:29 #25426January 30, 2020 at 17:16 #25449
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.