Forum Replies Created
-
Posts
-
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.logand/usr/NX/var/log/nxupdate.log(if it exist) files. Output from commanduname -aand screenshot of window with Authentication Error will be very useful. Send those information to forum[at]nomachine[dot]com, please.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 inC:\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?
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
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.
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/runand write those lines inside:#!/bin/bash exec /usr/NX/bin/nxexec /etc/NX/nxserver --daemonNote that if you installed NoMachine in different location than
/usr/NXyou need to replace/usr/NX/bin/nxexecto<place NoMachine is installed>/bin/nxexecWhen 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/Hello,
For starting NoMachine in init script please try command/usr/NX/bin/nxexec /etc/NX/nxserver --daemon & > /dev/null 2>&1In the meantime we are looking for some more official solution.
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.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.debFirst 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.
bash: /home/kevin/.xsession-errors: Permission denied
Try
sudo cat /home/kevin/.xsession-errors > /home/kevin/logs.xsession-errorsand send/home/kevin/logs.xsession-errorsfile 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.
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 commandsudo cp /usr/NX/share/applnk/server/xdg/NoMachine-* /usr/share/applications/.To check what caused that problem file
~/.xsession-errorswill be very useful. Please collect this file and send this information to forum[at]nomachine[dot]com.Hi, we are trying to reproduce the issue. Which version of desktop do you have? Cinnamon, MATE or XFCE?
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 startxfce4and then navigate to /usr/NX/etc/node.cfg and check if DefaultDesktopCommand key is set to path you got fromwhichcommand. It should look similar to this:
DefaultDesktopCommand "/usr/bin/startxfce4"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 nomachinethen remove leftover catalog by commandrm -rf /usr/NX/and install it again. This should fix the problem with authentication.