- This topic has 3 replies, 3 voices, and was last updated 1 year, 9 months ago by
.
-
Posts
-
I’ve read some old posts on this problem but I occasionally encounter it when I am on a connection with higher latency, on current builds. My use case involves using NoMachine across oceans. While I don’t mind slow responsiveness (it is expected), the NoMachine behavior of spewing repeat keypresses on the server side has in the past caused me great inconvenience when doing certain things.
Typing “Hello” but getting “Heeeeeeeeeeeeeeeeeeeello” isn’t so bad, but pressing Backspace once then getting 50 Backspaces results in data loss. I’ve had unwanted up/down/left/right repeats screw me up as well while editing documents.
Could this be made more robust somehow? My feeling is that it is easily reproducible simply by connecting to a server far, far away.
I’m using the current consumer Linux products, but this has happened to me under Windows as well.
I’m using the current consumer Linux products, but this has happened to me under Windows as well.
Do you mean that you can also reproduce it when connecting to Windows ? Or are you always connecting to Linux hosts and you reproduce it regardless of what OS you are connecting from?
If the server side is always Linux, do you have Wayland or X.org running there?
I’ve had this happen in the past (~2 years ago) when I was primarily using Windows 10 hosts and clients. These days I am primarily using Linux Mint XFCE hosts and clients which I believe are X?
Hi Rey,
sorry for the delay. What you describe shouldn’t happen normally as NoMachine already suppresses unwanted repeated keys. To investigate further your specific case we would need more info about your setup, in particular we would need to confirm if the server is using X or Wayland. If it’s more convenient for you, we could get such info from the logs. If you are willing to provide them, please follow the instructions in https://kb.nomachine.com/AR07K00677 and send them to forum[at]nomachine[dot]com, by referencing this topic.
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.