Bilbotine

[Bilbotine]

Hello Marcin,

We have opened a Trouble Report for this issue (you can check it here), and we will soon send you (via email) a patch with a fix.

[Bilbotine]

Hi Nineteen Sixtyone,

Thank you for the suggestion!

Adding multi-touch support for Linux – and the other OSes that we support – is not in our plans for the moment, but we are taking your request into consideration.

We’ll let you know if this feature is implemented in the future.

[Bilbotine]

Hello AXY,

Thank you for the information you provided on your set-up. Version 6 is now legacy, so you would need to update to a supported version – ideally you should be on at least NoMachine 8.x, and 8.18 is the latest. Then it will be possible to update cleanly to a version 9.

Your admin staff should be able to help you out, if you are not getting the updates. And if they need assistance, they can of course reach to us via the traditional support channel. Our Support team will be able to provide assistance.

Once the update to a supported version is done, please try NoMachine Network to access the machines, in order to exclude any eventual slowness introduced by the machine traversed and the VPN setup.

There is a 7-days free evaluation available upon creation of an account – see here for more details ; if you already have an account, please contact our Sales Team at sales(at)nomachine(dot)com.

[Bilbotine]

Hello rocky9_nomchine,

Thanks for the logs, we checked them, but we need more info. Can you please

• restart the server (/usr/NX/bin/nxserver –restart) and collect debug logs again as you already did (so that also the logs from the server daemon will be included)
• give us the output of ‘ps -ef’
• check whether the monitors are turned on and display is not sleeping

[Bilbotine]

Hi graphixillusion,

Thank you for your reply. Our developers are looking into it.

[Bilbotine]

Hi Gia,

It’s a normal behaviour, the admin password that you mention would be your sudo password.

Did you try with your sudo password already? If not, please do and let us know if it worked.

[Bilbotine]

Hi Geo1234,

Thanks for reaching out.

Unfortunately, we are not able to reproduce this issue. Can you please describe us the exact step-by-step instructions to reproduce the problem ?

Also, can you tell us if the Ubuntu server runs with Wayland or X11 ?

[Bilbotine]

Hi daedalus,

Thank you for following up 🙂

We had to prioritize other features for the NoMachine development roadmap moving forward and this particular one didn’t make the list, mainly because other ways exist to transfer files which can be used which Britgirl explained. It has not been completely excluded, but right now it’s not on our current roadmap.

[Bilbotine]

Hi Steve,

We are glad to know it’s solved.

[Bilbotine]

Hi Steve,

Q1- This is a problem that is known (https://kb.nomachine.com/TR04W11312), we already fixed it in V9, and it has been solved in V8.17 that was released a few days ago.

Q2- You can find all the Acronyms of NoMachine server subscriptions V9 in this article: NoMachine – NoMachine Subscription Acronyms And Support Levels – Version 9 – Knowledge Base

Q3- Unreachable means that due to any reason, the ECS cannot connect to the node. They can see more information when running for ex. sudo /etc/NX/nxserver –nodeinfo M.7 (name, IP or UUID of the node)

Q4- Updating the license of an expired product is possible, but in case of ‘unreachable’, it means that the ECS cannot connect to the node, and therfeore cannot handle license update.

Q5- The administrator can connect and replace a licence even when the software is expired, but updating a license before its expiry is recommended in order to avoid the issues highlighted in the point 4.

[Bilbotine]

Hi Frank,

Thanks for this update; can you please send us logs with debug enabled to allow us to investigate deeper the problem ?

Follow the instructions in this document: https://kb.nomachine.com/DT07S00243. It’s valid for v9 as well.

If possible, restart the Linux machine before reproducing the issue, and wait a minute after the logout.

Kill the nxnode process, so we can see exactly why the process restarts.

Gather logs again, and send them to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email.

[Bilbotine]

Hello again Steve,

We are not able to reproduce the problem.

Can you run this command on the SBTS: sudo grep AvailableSessionTypes /usr/NX/etc/*cfg

And let us know the result ?

[Bilbotine]

Hi SimpleTechGuy,

There is no bother 🙂

We’re glad the issue is solved.

[Bilbotine]

Hi Dan,

Thank you for reporting this issue.

It will be fixed in the next update.

[Bilbotine]

Hi Frank,

NoMachine starts an nxnode process as every user, to be able to manage his physical session.

When a user physically logs out from the desktop, and if the desktop is on login window, nxnode will be running with for example ( gdm, ssdm, or lightdm ).

[Author]

Posts