hawk

[hawk]

We are still investigating this issue.

Are you using this machine as a headless environment, running it in NoMachine virtual
desktop session or some other remote method or you are connecting to a physical session?

If you are not connecting to the physical display with Wayland enabled you can try disabling EGL
capture by command sudo /etc/NX/nxserver --eglcapture no and getting rid of LD_PRELOAD env by command unset LD_PRELOAD

Thank you for your patience.

[hawk]

Hello Jumpingmanjim,
May i ask you to share some information i asked above?
– please share example snap app that is causing the problem.
– are you connecting to a headless environment?
– which graphical shell you are using?

Also i will be grateful if you send us nx_journal.log from command sudo journalctl > nx_journal.log. Send those information to forum[at]nomachine[dot]com, please.

[hawk]

One more thing. Some useful information about things blocked by apparmor can be stored in journalctl. Please run sudo journalctl -g apparmor > apparmor.log command, collect apparmor.log and send it to forum[at]nomachine[dot]com along with other informations.

[hawk]

Hello Ilgaz, fajny.masz.tornister and amprince01
May i ask you for more information?
– please share example snap app that is causing the problem?
– are you connecting to a headless environment?
– which graphical shell you are using?
Logs from /usr/NX/var/log/ directory and output from command env | grep -i nx may be very useful. Send those information to forum[at]nomachine[dot]com, please.

[hawk]

Hello,

You can limit rule for nx user to run only specific commands.

Try to replace:

nx ALL=(ALL) NOPASSWD: ALL

to:

nx ALL=(ALL) NOPASSWD: /usr/NX/scripts/custom/start_de.sh, /usr/NX/scripts/custom/stop_de.sh

Please inform if this worked and if this is satisfying enough.

[hawk]

Hello, we are reproducing similar issue but it looks like it is not caused by NoMachine in any way. For confirmation please collect /usr/NX/var/log/nxinstall.log and /usr/NX/var/log/nxupdate.log (if it exist) files. Output from command uname -a and screenshot of window with Authentication Error will be very useful. Send those information to forum[at]nomachine[dot]com, please.

[hawk]

Hello,

Can you send us the NoMachine log directory? By default it is C:\ProgramData\NoMachine\var\log\ (%PROGRAMDATA%\NoMachine\var\log). If the logs are not there you can try to collect them from %TEMP% directory which is typically located in C:\Users\<user>\AppData\Local\Temp\Setup Log... Two latest should be enough.

Note that ProgramData and AppData are hidden by default.

Can you also try new version 8.8.1 available on http://www.nomachine.com?

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

[Author]

Posts