- This topic has 8 replies, 2 voices, and was last updated 1 week, 2 days ago by
.
-
Posts
-
I am running Server 9.3.7 on Ubuntu 18.04 with a Jetson Nano (original) and LXDE. I connect to this with Client 9.3.7 from Windows 11 Pro (25H2).
When I open an lxterminal for command input, the client only echoes the characters I type every second keystroke! I can see on the server machine’s physical display that all the keystrokes are being received in a timely manner, it is just that the client does not show them except in pairs. That is, I type “p” on the client and “p” is shown, then I type “w” but the client does not show this (although the server has clearly received it), then I type “d” and suddenly the client shows “wd” (i.e. the new key plus the previously non-echoed key).
This was not a problem under version 8, but I can no longer find any old DEB package to revert my Linux server.
Hi, we’re not able to reproduce similar behaviour on the latest release. You could try disabling hardware decoding on the Windows client to start off with. Instructions are here: https://kb.nomachine.com/AR07U01202.
If that doesn’t help can you send us the logs of the NoMachine server? Please set log level to debug, restart and then reproduce. Full instructions are here: https://kb.nomachine.com/DT08U00298. Send them to forum[at]nomachine[dot]com using the title of this topic as the subject of your email.
We can send you a link to a v8 package (can you remember which specific version? otherwise we’ll send the most recent one). That way you can verify that the problem is not there. In that case, we would appreciate logs from the v8 server as well, so we can compare. Thank you!
So I set the Server log level to Debug, restarted the server, and the error is gone. However, I then restored the log level to Standard, restarted again, and the problem reappeared. Why should just adjusting the log level cause/alleviate this problem?
If you could give me a link to the DEB package for 8.15.3 for arm64 (or aarch64) that is about what I had been using previously.
I’m sending you the link. Check your inbox.
For v8 logs, please use this link instead https://kb.nomachine.com/DT07S00243.
Hi again, just to clarify here because I gave some instructions in the email but did not write them here. Do try disabling HW decoding on the Windows client before doing what’s explained below.
If that doesn’t help, send in the logs from the v9 installation set to Standard, plus the player logs from Windows. Then, using the link I sent to you for the server, try to reproduce on v8. If it works well, send us complete logs, so we can compare with the logs from the v9 installation.
The zipped server log from Linux 9.3.7 was 12MB and this web interface refused it as too big. Maybe there is some subset of the server logs that is most useful?
I could not get the W11 9.3.7 client logs at all using the GUI — every time I requested them the client/player crashed (and no files were written). Also, the size of the C:/Users/nomachine/.nx directory is 58MB (uncompressed), so posting this will likely be a problem.
In NoMachine 9.3.7 the problem persists even when HW decoding is disabled in the W11 client.
After uninstalling both client and server then reinstalling older version 8.15.3 on both sides, the problem remains.
Overall, I think this weird echo pattern might not have anything to do with NoMachine at all. It also shows up in [removed], so perhaps it is something in the X11 system that became configured incorrectly.
Send the logs to forum[at]nomachine[dot]com. Just use the title of this topic as your subject. We’ll take a look to see what’s happening.
Hi, the logs are actually clean. We think it stems from your system, and probably the drivers on your Ubuntu machine. You have some options to try:
1) check what video drivers your system is using and if they can be updated
2) try the Workstation evaluation and see if that fixes the issue
3) if you want to stick with the free version, then you can try switching off the x server and use the NoMachine’s own virtual display – more instructions are here: https://kb.nomachine.com/AR03P00973. If you choose this option, you won’t have access to the physical display as you do now.
You must be logged in to reply to this topic. Please login here.