Britgirl

[Britgirl]

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

[Britgirl]

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 -m in 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 dir you 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/NX

and install again.

[Britgirl]

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/AR03M00842

For Raspberry: Installation & configuration notes for NoMachine Linux Raspberry Pi packages
https://kb.nomachine.com/AR07N00896

To check what architecture your device is based on, open a terminal on your device and run the uname -m command.

[Britgirl]

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 token

Here is the link to the other topic: https://forums.nomachine.com/topic/first-time-connecting-session-negotiation-failed-error#post-34887

 

[Britgirl]

Thanks for the update. Although having done two tweaks together, it’s not clear which one helped.

However, further investigation on our side shows that this behaviour is reproduced on Ubuntu 20.04 and it’s reproducible even without NoMachine being involved, also by other users on other forums. This seems to show that, whether it’s a bug or the intended behaviour, the video card works in “slowed down mode” when the screensaver is activated, or it goes into sleep status. It’s not caused by NoMachine.

[Britgirl]

Which package did you install from the website, and for 32-bit or 64-bit?

[Britgirl]

What you see in the image that I posted is Firefox session using NoMachine’s custom session on Linux. I.e connecting to a Linux desktop but requesting a rootless window or single application. This is a feature available in our Linux Terminal Server products by selecting ‘Create a new custom session’ and inserting the name of the application in the field ‘Run the following command’.

Check the tutorial here for: https://www.nomachine.com/creating-new-virtual-desktop-sessions

The products we offer for remote access to Windows/macOSgive you access to the physical desktop running there. It is not possible to access single applications.

Attachments:

1. 

   floating-window-firefox.png
   

[Britgirl]

Is what you want like what is in the attached image?
In the image you can see:

1 x window of local Windows native browser
1 x NoMachine session window of Firefox browser (this is running on a remote server)

Attachments:

1. 

   ff-rootless.png
   

[Britgirl]

Hi, did you reinstall and reboot? And you still cannot connect?

If you’ve done that, then you need to enable debug (nxserver --debug enable) and resubmit the logs from the server side again. Please make sure you follow the instructions as per the document https://kb.nomachine.com/DT11R00182 making sure you enable first, reproduce the issue and then extract the logs. Please also submit the client side logs (by selecting Don’t delete log files on exit in the Player).

[Britgirl]

Can you enable cursor showing?

Start a connection, open the Connection Menu (Ctrl-Al-0) -> Input -> Tick the box for “Show remote cursor pointer”. If that doesn’t help, please send us the server-side logs. Please follow the instructions here https://kb.nomachine.com/DT11R00182 and then send them to forum[at]nomachine[dot]com.

[Britgirl]

The logs would be useful. We will keep this topic open for a few more weeks. When you get a chance to submit the logs, please attach them here or send directly to forum[at]nomachine[dot]com.

[Britgirl]

Please show us the output of:
$ sudo netstat -anlp | grep egl

If it’s empty,  enable egl capturing with sudo /etc/NX/nxserver --egl-capture yes. What does the output of grep egl after enabling? (this is to check that egl capture is being pre-loaded).

Then, on the server, log out from the desktop, log back in and then start a NoMachine connection. What happens?

[Britgirl]

Hi, we have not been able to reproduce the behaviour that you have described above. You could try connecting to another desktop from the same iPad to check if you have the same problems. Also check whether the language set on the iPad keyboard is the same as the one set on the system keyboard on the Raspberry.

[Britgirl]

Jigglywiggly, this could be a different issue?

Pressing the Super key doesn’t work, you say. To do exactly what? Is Ubuntu 22.04 the client or is it the server? More details about your set-up (OS, version and NoMachine products) would be useful. Also, what kind of session are you running?

[Britgirl]

Hi,

can you tell us the macOS version you are connecting from and the distro of the Linux server that you are connecting to (you mentioned it in a duplicate topic you submitted), just so we have all the details?

In the meantime, on the Mac machine you can disable the nxserver from the command line.

On Mac:

sudo /etc/NX/nxserver --shutdown

sudo /etc/NX/nxserver --startmode manual

 

Check this article for further details. It also describes the manual procedure (by editing /Library/LaunchDaemons/com.nomachine.server.plist file) for advanced users.

https://kb.nomachine.com/AR04L00800

[Author]

Posts