hawk

[hawk]

Hello,
NoMachine creates a hidden account, the nx user, used for internal operations of the NoMachine server only. This user, however, should not appear in the list of available users on login screen, as it’s hidden. It cannot be used to log-in to the Mac also.  We cannot disable “Other Users” option in NoMachine installation process but you can do it yourself by using command in your terminal.
To disable “Other Users” option please type:
sudo defaults write /Library/Preferences/com.apple.loginwindow SHOWOTHERUSERS_MANAGED -bool FALSE

If you want to enable it back use:
sudo defaults write /Library/Preferences/com.apple.loginwindow SHOWOTHERUSERS_MANAGED -bool TRUE

However we think that ‘nx’ user on the list in “Users and Groups” preferences need more investigation and we will take a look what we can do with it.

[hawk]

Hi, there are two ways to disable automatic update in NoMachine.

One way is to edit /Library/Application\ Support/NoMachine/var/db/update file. Just change number in second section to 0. You can do this by running command: sudo sed -ie ‘s/:[0-9]*:/:0:/‘ /Library/Application\ Support/NoMachine/var/db/update from your terminal.

Second way is to open Server Preferences -> Updates from your NoMachine Player Settings and uncheck Automatically check for updates checkbox.

• This reply was modified 5 years, 9 months ago by hawk.

[hawk]

Unfortunately we will need some additional information. Those should tell us where the real problem is. Please collect /usr/NX/var/log/nxinstall.log and /usr/NX/var/log/nxupdate.log (if it exist) files, send those information to forum[at]nomachine[dot]com, please.

Additionally we will need full name of NoMachine package which you are trying to install, information if you are installing NoMachine from terminal command or by double-clicking the package and which architecture of Ubuntu you have installed.

[hawk]

Hello, we are not able to reproduce the problem. To investigate this we need software update logs.

To collect logs fom software update you need to enable “Don’t delete logs on exit” in “Player Preferences” -> “Privacy” and then he need to try reproduce the error, if error will reproduce we need logs from /Users/<user>/.nx directory.

To properly collect those logs you can take a look on this article https://www.nomachine.com/DT04M00076#6

[hawk]

Thank you for reporting this problem. We fixed this issue immediately on our update servers and opened a Trouble Report to track this issue: https://www.nomachine.com/TR08N07156. To fix unsigned files we strongly recommend to update your existing installation by installing NoMachine 6.0.78 package from our website (even if you have this version already).

[hawk]

Thank you for reporting this problem. We have opened a Trouble Report to track this issue: https://www.nomachine.com/TR11O08293. To let the installation complete without errors please temporarily change name or backup and remove “/etc/lsb-release” file (it can be restored after installation/update of NoMachine) as the user “jayltee” instructed.

 

To be notified when the fix is released, you may register to the ‘Notify me when the TR is closed’ option.

[hawk]

Hello,

Unfortunately NoMachine does not support two different versions of NoMachine Enterprise Client installed on one Windows. It will automatically find and update existing NoMachine.

[hawk]

You can check it directly in your license files: /usr/NX/etc/server.lic and /usr/NX/etc/node.lic.

NoMachine Free license from v. 3.5.0 has line “Product:            NX Free Edition Node” in node.lic file and line “Product:            NX Free Edition” in server.lic file.

NoMachine Free in versions 4 – 6 has line “Product:                NoMachine Node” in node.lic file and line “Product:                NoMachine” in server.lic file.

[hawk]

Thank you for reporting this problem and the detailed analysis. We are still investigating this issue because we weren’t able to reproduce it. We will open a Trouble Report and inform you about it as soon as possible.

 

[hawk]

We see that you still have an old 3.5.0 license for NX free edition in place, which is no longer supported in version 6.

We suggest to change names of /usr/NX/etc/server.lic and /usr/NX/etc/node.lic to /usr/NX/etc/server.lic.old.backup and /usr/NX/etc/node.lic.old.backup before update to v. 6.

or

uninstall NoMachine software, remove the /usr/NX directory and install again package NoMachine v. 6.

[hawk]

Hello, to investigate the problem, I would need some additional information:

 

1) Please execute commands:

ls -ltr /usr/NX/etc/

sudo cat /usr/NX/etc/*lic

 

2) Provide also the following files:

/usr/NX/var/log/nxinstall.log

/usr/NX/var/log/nxupdate.log

 

You can attach output and logs here or send them to forum[at]nomachine[dot]com.

[hawk]

@davidblumenthal From logs and informations you sent us, we are sure that you have installed x32 package (nomachine_5.1.9_7_i386.deb) on x64 Ubuntu which don’t have support for x32 architecture packages (unless you will install x32 libraries from ubuntu repository).

To fix it you need to uninstall actual package by sudo dpkg --purge nomachine, then remove all leftovers by executing command: rm -rf /usr/NX/ /var/NX/ /etc/NX/ and install x64 package from our website (nomachine_5.1.9_6_amd64.deb).

[hawk]

Hello,

We aren’t able to reproduce your problem in our lab. We need more details. Could you run below commands, collect some logs and send output to forum[at]nomachine[dot]com, please?

1) lsb_release -a

2) uname -a

And we need nxinstall.log and nxupdate.log from /usr/NX/var/log/ directory. The proper way how to do this is explained inside this link https://www.nomachine.com/DT07M00098 .

[hawk]

Unfortunately we will need some additional information. Those should tell us where the real problem is. Please run:

1) md5sum nomachine-workstation-update_5.0.47_3_x86_64.rpm
(run this command in the same place you was running command “rpm -Uv nomachine-workstation-update_5.0.47_3_x86_64.rpm” please)

2)ls -ltr /etc/NX/ /etc/NX/server/localhost/

and collect /usr/NX/var/log/nxinstall.log and /usr/NX/var/log/nxupdate.log (if it exist) files, send those information to forum[at]nomachine[dot]com, please.

• This reply was modified 9 years ago by hawk.

[hawk]

Hello,

We aren’t able to reproduce your problem in our lab. We need more details. Could you run below commands, collect some logs and send output to forum[at]nomachine[dot]com, please?

1) /usr/NX/bin/nxserver --version
2) ps aux | grep nx

And we need whole /home/<your_user>/.nx directory. The proper way how to do this is explained inside this link https://www.nomachine.com/DT04M00076#5

• This reply was modified 9 years ago by hawk.
• This reply was modified 9 years ago by hawk.

[Author]

Posts