Forum Replies Created
-
Posts
-
We suspect the wget command failed because the nomachine.deb file that exists there is the armhf file. So remove current installation again and this time try:
wget -O nomachine.deb https://download.nomachine.com/download/8.16/Raspberry/nomachine_8.16.1_1_arm64.debagain.Hi, no there aren’t any graphical restrictions.
Can you submit a screenshot of what you actually see?
Previous reports have revealed that Raspberry Pi reports a 64-bit kernel. This is why uname -m command shows aarch64. However, the OS is actually 32-bit-based. Could you try installing a package suitable for ARMv7?
Links to similar posts:
https://downloads.nomachine.com/download/?id=108&distro=Raspberry&hw=Pi3
I see you used
ssh-keygen -m PEM -t rsa -b 4096to generate the keypair.Did you try to use a keypair generated by running:
ssh-keygen -t rsa -b 4096?Hi, it sounds very similar to this bug report.
Cannot login by NX protocol and private key when option ‘Import the private key to the connection file’ is checked
https://kb.nomachine.com/TR05S10271As a temporary workaround, do not check option ‘Import the private key to the connection file’ in the UI.
We have been unable to reproduce this same behaviour. Logs show an error similar to when the machine is not rebooted, but we know that you did reboot. Ideal would be to debug deeper with a debug package that we would create. If you are interested, let us know. In the meantime we will continue investigating.
Hi, are you able to send us the server-side logs so we can check them? Please enable debug and reproduce the problem by connecting to that Linux Mint server. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com or post them here. Please use the title of this topic as the subject of your email.
The logs show a possible crash of the nxnode process, which is unusual, so it would also be useful to have the backtrace. Please see the following article for instructions on how to get any core files https://kb.nomachine.com/AR09L00810Thanks!
Hi, we were able to reproduce the same issue and a fix is scheduled, not for the next release but the one after that. We’ll publish the Trouble Report to track soon.
Hi, is there a monitor attached to the Linux Mint machine you are connecting to?
Is the image of the desktop you see totally frozen? Or do you see some screen changes when you are connected?
Logs would be useful. On the Newby machine, enable debug and try to reproduce. Please follow the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com or attach here. Please use the title of this topic as the subject of your email. Thanks!
Thanks for the logs, they were helpful. We have reproduced the same behaviour on one of several hundred test machines we have in our labs and we are actively working to find a solution.
The logs didn’t show any NoMachine errors or misbehaviour, so this could be an indication that there is a problem with the drivers.
Hi, it is the expected behaviour. UDP is not used in floating window mode because in this mode NoMachine always uses X11 vector graphics. More about “The X11 vector graphics mode in X-Window virtual desktop” is available here if you are interested: https://kb.nomachine.com/AR02L00779.