Forum Replies Created
-
Posts
-
We are not aware of similar issues on Debian 11.
The “S-log” excerpts you pasted are not from NoMachine. If you have an NX legacy or derivative installed on that machine, or had it installed, I would suggest to uninstall NoMachine and remove all traces including the home, reinstall NoMachine and start again, making sure that you’ve also removed any trace of what other product you might have had (even inadvertently) on that machine.
sudo dpkg --purge nomachine sudo rm -rf /usr/NX /etc/NX /var/NX .nxThen reinstall the NoMachine product of your choice.
You should check server-side logs (which are in /usr/NX/var/log) – not client.
For your reference:
Collect server side logs automatically
https://kb.nomachine.com/DT11R00182or
Collect server and client logs manually
https://kb.nomachine.com/DT11R00181Default Ubuntu 20.04 installs and works out-of-the-box in our labs.
Are you running Wayland and is it a VM? If so, take a look at this article and follow the tips there:
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://kb.nomachine.com/AR04R01083You could also log out and then log in, but to a X.org desktop. This will show whether the problem is Wayland or not.
Send the logs by all means, we can take a look and see what’s going on. Please send them to forum[at]nomachine[dot]com making sure to put the title of your topic as the subject of your email. Thanks!
The output shows that PulseAudio libs are present but not that PulseAudio is installed and being used. Fedora 36 now adopts Pipewire instead of PulseAudio and it is likely that it is using those libraries.
https://fedoraproject.org/wiki/Changes/DefaultPipeWire
Support for Pipewire in NoMachine will be added in v8.
So first install PulseAudio:
sudo dnf install pulseaudioFedora will ask you to remove Pipewire and replace it with PulseAudio. Then you can install NoMachine again or use command from installation output:
/usr/NX/scripts/setup/nxnode --audiosetup <path>to configure PulseAudio with NoMachine.
Hi, thanks for reporting this. We’ve also reproduced it on the iPadOS 16 beta. We will queue up for fixing in our next mobile release.
Can you please submit the screenshots as separate attachments? They won’t be accepted if you try to paste them in to your reply. Thanks.
Hi, please check this topic here which deals with the same message.
First, can you check that the correct permissions are set on the Mac computer? Here you can find some further hints: https://knowledgebase.nomachine.com/AR09S01139. In some cases, after a OS update, it might be necessary to remove (uncheck) the permissions and grant again.
If that doesn’t help, it could be the same issue we are already aware of and will be fixed in the next software release, version 8. A restart of the nxserver on the Mac machine can sometimes help.
After you’ve tried this, what happens?
Hi, the available resolutions in the Display settings of the connection menu are those which are supported by your OS’s system configuration. Therefore, and provided I’ve understood what you are trying to achieve, what you need to do is change the orientation on your Windows machine to allow NoMachine to show the content in portait mode.
See this page on the Microsoft website:
https://support.microsoft.com/en-us/windows/change-screen-orientation-f7ab1ff8-971d-58a5-b8ee-bc113bbf3acb#WindowsVersion=Windows_10Does this help?
We have no issues installing on Fedora 36.
Did you install over having previously installed/uninstalled another NoMachine product?
Try uninstalling cleanly with
sudo rpm -e nomachine sudo rm -rf /usr/NX /etc/NXand install again.
This is possible with the Enterprise products. Connect to your remote desktop using a simple Web browser from any device. Try NoMachine Enterprise Desktop to start with 🙂
https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Desktop
64 is what I intend but tried both
if you have 64-bit architecture and installed the packages for 32-bit, you will get an error and vice-versa. Please check this on the machine you want to install on. You can do this by running
uname -min a terminal.If it shows: x86_64, you need amd64 deb which is here: https://www.nomachine.com/download/download&id=3
Is this what you installed?If you have tried installing different packages, and then uninstalling without removing
/usr/NX diryou may have some leftovers from the wrong 32-bit package which need clearing out. It would be a good idea to start from scratch.sudo dpkg --purge nomachine sudo rm -rf /usr/NX /etc/NXand install again.
It’s difficult to say without knowing additional details such as what ARM device you have and what package you downloaded.
What Linux distribution and version is installed on your ARM device. What device is it? What architecture ( ARMv6, ARMv7, ARMv8)
This error generally appears when you use the wrong password. Sudo username and its password are requested when making changes to the nxserver. Did you see the prompt?
We have an article in our Knowledge Base specifically for devices which are not Raspberry.
Installation & configuration notes for NoMachine Linux ARM packages
https://kb.nomachine.com/AR03M00842For Raspberry: Installation & configuration notes for NoMachine Linux Raspberry Pi packages
https://kb.nomachine.com/AR07N00896To check what architecture your device is based on, open a terminal on your device and run the uname -m command.
Apologies, I thought I had answered.
Your issue looks similar to another topic, and it’s related to required privileges which are missing. It appears that ‘nx’ user doesn’t hold the privilege required for starting the nxnode process. In this case, most likely ‘Act as part of the operating system’ is missing. This is the list of all privileges needed by ‘nx’ account:
– Act as part of the operating system
– Log on as a service
– Adjust memory quotas for a process
– Replace a process level tokenHere is the link to the other topic: https://forums.nomachine.com/topic/first-time-connecting-session-negotiation-failed-error#post-34887