hawk

[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]

Any idea of I could package this for Void Linux or would I have to read the license and make a determination for that?

I’m not sure if i understand correctly. Do you want to rebuild NoMachine package to add support for Void Linux or do you want to redistribute? Redistribution of NoMachine packages is not allowed by the terms of the EULA.

[hawk]

As promised, here is a more official solution.

To create working NoMachine script for Runit you need to follow these steps. Note that you need root permission to perform those actions.

First please create runit directory for nomachine. You can do this by command mkdir /etc/sv/nomachine/.
Next you need to create file /etc/sv/nomachine/run and write those lines inside:

#!/bin/bash

exec /usr/NX/bin/nxexec /etc/NX/nxserver --daemon

Note that if you installed NoMachine in different location than /usr/NX you need to replace /usr/NX/bin/nxexec to <place NoMachine is installed>/bin/nxexec

When the file is created you need to set execute permission by chmod +x /etc/sv/nomachine/run.

Last command will create link for service and enable it:
ln -s /etc/sv/nomachine /var/service/

[hawk]

Hello,
For starting NoMachine in init script please try command /usr/NX/bin/nxexec /etc/NX/nxserver --daemon & > /dev/null 2>&1

In the meantime we are looking for some more official solution.

[hawk]

Hello,
NoMachine do not provide feature to block commands. You can do this by configuring sudoers file for example.
http://www.tecmint.com/disable-shutdown-and-reboot-commands-in-linux/

About xscreenserver problem we are unable to reproduce the problem. Please check if changing DefaultDesktopCommand key value in /usr/NX/etc/node.cfg (on server side) from “/usr/bin/startxfce4” to “dbus-launch /usr/bin/startxfce4” will fix the problem. You need to have root permissions to change values in NoMachine configuration files.

If this will not help some logs may be helpful. Please run command sudo grep xscreensaver /var/log/secure* and send us output to forum[at]nomachine[dot]com, referencing the topic as subject.

[hawk]

Installation seems to be corrupted and we are unable to track the issue. Please reinstall it completely. You can do this by running those command in given order:
sudo dpkg --purge nomachine
sudo rm -rf /usr/NX/ /var/NX/ /etc/NX/
sudo dpkg -i nomachine_6.11.2_1_amd64.deb

[hawk]

First command:

sudo cat /home/kevin/.xsession-errors > /home/kevin/logs.xsession-errors

created file named logs.xsession-errors in your home directory.

To collect nxserver logs please use those commands in terminal in given order:
sudo sed -i 's/#SessionLogLevel 6/SessionLogLevel 7/g' /usr/NX/etc/server.cfg
sudo /usr/NX/bin/nxserver --restart
sudo tar cvfz NoMachine-log.tar.gz /usr/NX/var/log/

Those command will create file named NoMachine-log.tar.gz in you home directory.

Please send us those both files (NoMachine-log.tar.gz, logs.xsession-errors) to forum[at]nomachine[dot]com, referencing the topic as subject.

[hawk]

bash: /home/kevin/.xsession-errors: Permission denied

Try sudo cat /home/kevin/.xsession-errors > /home/kevin/logs.xsession-errors and send /home/kevin/logs.xsession-errors file to forum[at]nomachine[dot]com.

About the second problem we will need NoMachine logs. To properly collect those logs you can take a look on this article https://www.nomachine.com/DT10O00163#1.1 and also we will be grateful if you send those logs to forum[at]nomachine[dot]com, referencing the topic as subject.

[hawk]

We are still unable to reproduce the problem. Please check if NoMachine menu files are on the right direction by command sudo ls -ltr /usr/share/applications/ | grep NoMachine. If output will be empty you can fix it by command sudo cp /usr/NX/share/applnk/server/xdg/NoMachine-* /usr/share/applications/.

To check what caused that problem file ~/.xsession-errors will be very useful. Please collect this file and send this information to forum[at]nomachine[dot]com.

[hawk]

Hi, we are trying to reproduce the issue. Which version of desktop do you have? Cinnamon, MATE or XFCE?

[hawk]

We will need your node.cfg file so we can verify if file is complete. You can find it at /usr/NX/etc/node.cfg, then send those information to forum[at]nomachine[dot]com, please.

Also please verify if your default desktop command is set properly. First check what is the path to startxfce4 by using command which startxfce4 and then navigate to /usr/NX/etc/node.cfg and check if DefaultDesktopCommand key is set to path you got from which command. It should look similar to this:
DefaultDesktopCommand "/usr/bin/startxfce4"

[hawk]

I was able to reproduce the issue and unfortunately previous problem caused installation damage and it is hard to fix without reinstalling NoMachine.

To completely reinstall NoMachine you need to use command sudo dpkg --purge nomachine then remove leftover catalog by command rm -rf /usr/NX/ and install it again. This should fix the problem with authentication.

[hawk]

NoMachine setup is using command install for copying and setting files. As install is replaced on your machine files are installing incorrectly. Please rename /bin/install to for example /bin/inst (by command mv /bin/install /bin/inst) and try to install NoMachine again.

[hawk]

As you can see your install command is replaced by some script that is trying to use apt. install is a basic command used on all linux distributions for copying files and should not be replaced. To fix this issue you need to check if install command is not replaced by alias (alias | grep install and if it’s on the list unalias install). If it’s not replaced by alias please change name of /bin/install file and try to install NoMachine again.

Output from install --help command should look like this:

install --help
Usage: ./install [OPTION]... [-T] SOURCE DEST
  or:  ./install [OPTION]... SOURCE... DIRECTORY
  or:  ./install [OPTION]... -t DIRECTORY SOURCE...
  or:  ./install [OPTION]... -d DIRECTORY...

This install program copies files (often just compiled) into destination
locations you choose.  If you want to download and install a ready-to-use
package on a GNU/Linux system, you should instead be using a package manager
like yum(1) or apt-get(1).

In the first three forms, copy SOURCE to DEST or multiple SOURCE(s) to
the existing DIRECTORY, while setting permission modes and owner/group.
In the 4th form, create all components of the given DIRECTORY(ies).

Mandatory arguments to long options are mandatory for short options too.
      --backup[=CONTROL]  make a backup of each existing destination file
  -b                  like --backup but does not accept an argument
  -c                  (ignored)
  -C, --compare       compare each pair of source and destination files, and
                        in some cases, do not modify the destination at all
  -d, --directory     treat all arguments as directory names; create all
                        components of the specified directories
  -D                  create all leading components of DEST except the last,
                        or all components of --target-directory,
                        then copy SOURCE to DEST
  -g, --group=GROUP   set group ownership, instead of process' current group
  -m, --mode=MODE     set permission mode (as in chmod), instead of rwxr-xr-x
  -o, --owner=OWNER   set ownership (super-user only)
  -p, --preserve-timestamps   apply access/modification times of SOURCE files
                        to corresponding destination files
  -s, --strip         strip symbol tables
      --strip-program=PROGRAM  program used to strip binaries
  -S, --suffix=SUFFIX  override the usual backup suffix
  -t, --target-directory=DIRECTORY  copy all SOURCE arguments into DIRECTORY
  -T, --no-target-directory  treat DEST as a normal file
  -v, --verbose       print the name of each directory as it is created
      --preserve-context  preserve SELinux security context
  -Z                      set SELinux security context of destination
                            file to default type
      --context[=CTX]     like -Z, or if CTX is specified then set the
                            SELinux or SMACK security context to CTX
      --help     display this help and exit
      --version  output version information and exit

The backup suffix is '~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX.
The version control method may be selected via the --backup option or through
the VERSION_CONTROL environment variable.  Here are the values:

  none, off       never make backups (even if --backup is given)
  numbered, t     make numbered backups
  existing, nil   numbered if numbered backups exist, simple otherwise
  simple, never   always make simple backups

GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
Full documentation at: <http://www.gnu.org/software/coreutils/install>
or available locally via: info '(coreutils) install invocation'

[hawk]

We have been unable to reproduce this problem. From logs you sent to us we have some conflicting information. One log says there are all files and have proper permissions set. Another log says that installation can’t find those files. Logs appear to be from two different machines, e.g one set from the connecting client, the other from the server. Also we did not received /usr/NX/var/log/nxinstall.log and /usr/NX/var/log/nxupdate.log which are essential to reproduce the problem in our lab.

You can also create detailed debug file which should tell us everything about the problem. You can do it by executing command sudo sed -i '20s/^/set -x\n/' /usr/NX/scripts/setup/nxnode && sudo /usr/NX/scripts/setup/nxserver --update > nxlog.txt 2>&1 && sudo sed -i "/set -x/d" /usr/NX/scripts/setup/nxnode from your terminal and then send us nxlog.txt which will be in the place you executed command above.

Please note that the logs must be from the machine where you are having installation problems.

[Author]

Posts