Forum Replies Created
-
Posts
-
We’ve opened a Trouble Report:
http://www.nomachine.com/TR04L04382
Sign up to receive notifications of when a fix is available.
We’re unable to reproduce this behaviour with the keyboard. Is it possible for you to connect to the server using a different client? Do you get the same behaviour?
Just updating this post after having received the logcat. The problem is that we don’t currently support the Tegra 2 which is what is used on your tablet. We’re working on extending supported platforms.
Did you follow the instructions which are linked from the above topic? https://www.nomachine.com/AR10K00710
Quoting from the article: “If you want to set a different display, change the node.cfg key: #DisplayDefault :0 by replacing the ‘0’ with the correct number.”
The original Feature Request is here: https://www.nomachine.com/FR10K02789
Are you able to SSH in to your RHEL machine from your laptop?
The logs would be useful from both sides to see what is happening. Please follow the instructions here and either attach them to your reply or forward them to issues[at]nomachine.com.
https://www.nomachine.com/AR07K00677
If you have had issues connecting to a 3.5.0 server from a version 4.2 client, you should submit further information via the link above. 3.5.0 issues are dealt with via the traditional support channels whereas the forums are dedicated to version 4 server/client questions.
You should update your version (both sides) because numerous issues in 4.1.x have since been fixed. Come and download 4.2.21.
I just wanted to add that NoMachine doesn’t set or add anything to your Linux environment. Anything related to your profile, a service or system setting, e.g. the screensaver in your case, doesn’t change because you installed NoMachine. So the fact your screensaver was activating itself after a very short time is not a bug of NoMachine. It was simply a setting in Gnome that had been configured incorrectly 😉
Further references: https://www.nomachine.com/AR11K0074
We’ve opened the following TR for this problem, and 4.2.21 will fix it.
Please update your server and client versions to the latest packages of NoMachine 4 and let us know if you are still having issues.
Will be fixed in the next release: https://www.nomachine.com/TR04L04356