kroy

[kroy]

Please try updating your NoMachine version. You can do it from GUI: click on NoMachine icon in the tray -> “Show the server status” -> “Server preferences” -> “Updates” -> “Check now”.

[kroy]

Can you send nx processes list with enabled option “Handles”?

Just run Process Explorer (Ctrl+Shift+ESC), choose “View” -> “Select Columns…” -> check “Handles” -> click “Ok”.

Now sort with name, scroll down list to see nx processes and do screenshot. You can attach the picture here or send to forum[at]nomachine[dot]com.

[kroy]

Packages for arm64 architecture will be available for download in the near future. At the moment we not support this architecture. But installation armhf is possible on your device. Multiarch lets you install library packages from multiple architectures on the same machine. So you just need to log as root and run following command:

dpkg –add-architecture armhf
apt-get update
apt-get install libstdc++6:armhf libgcc1:armhf zlib1g:armhf libncurses5:armhf
dpkg -i nomachine_5.1.44_1_armhf.deb

Like on instructions: https://wiki.debian.org/Multiarch/HOWTO

[kroy]

Are you using NoMachine client to connect? Which IP are you using? Did you tried to connect with IP from eth0?

[kroy]

Hi,
To change the default desktop environment in NoMachine virtual sessions, you can replace the value in the node configuration key DefaultDesktopCommand. To do that, edit /usr/NX/etc/node.cfg, uncomment DefaultDesktopCommand (if it’s commented) and change the value inside the quotes.

Change to KDE desktop:
DefaultDesktopCommand “/usr/bin/startkde”

Change to MATE desktop:
DefaultDesktopCommand “/usr/bin/mate-session”

There is also an other possibility: you can choose desktop between GNOME or KDE from list. To do that, edit the server configuration file. Uncommment ConnectPolicy and change the desktop value to 1. Now you can list all the desktop types set in the AvailableSessionTypes key.
Edit /usr/NX/etc/server.cfg and change:

#ConnectPolicy autocreate=1,autoconnect=1,automigrate=1,desktop=0,dialog=0

to

ConnectPolicy autocreate=1,autoconnect=1,automigrate=1,desktop=1,dialog=0

But as it is mentioned – it shows GNOME and KDE. MATE is not supported with this option for the moment. You can follow our Feature Request (https://www.nomachine.com/FR09L02833) and check the ‘notify me’ box to receive a notification when the feature has been released.

[kroy]

Thanks for the logs, but after changing value SessionLogLevel you need to restart nxserver (you can do it from NoMachine Player: click on NoMachine icon on system tray -> Show the connection status -> Connection -> Restart). After that, please reproduce the problem and send the logs from server side.

[kroy]

Is the pulseaudio process running on the device (ps -Af | grep pulseaudio)? If not please launch it (you can execute command: pulseadio) and restart the test.

[kroy]

You need to configure the system on client side to get a backtrace from the crashes. For example you can use this instruction: https://wiki.ubuntu.com/DebuggingProgramCrash. Try to reproduce problem and send backtrace to forum[at]nomachine[dot]com.

[kroy]

You need to install pulseaudio. After installation you may need to setup NoMachine. To do that you can enter the following commands:

sudo apt-get install pulseaudio
sudo /usr/NX/scripts/setup/nxnode --audiosetup

[kroy]

Can we see your logs? Please run debug, restart nxserver, reproduce issue and send all logs from server side to forum[at]nomachine[dot]com. You can find instructions about debug and collecting logs here: https://www.nomachine.com/DT04M00076.

Another thing to note is that even though no client is connected there is a consistent 20KB/second sending and receiving network activity.  Once I stop the server, that activity disappears.

On server side open NoMachine Player, choose settings. Next navigate to Privacy panel and check “Don’t show other computers on the network”. Then click on Server preferences on the bottom of the window. Then uncheck “Advertise this computer on the network”. Now restart nxserver and recheck network activity. Please let us know here if it helped.

[kroy]

Can you describe more the environment in which you work? Your clients (Windows 7, 10 and Linux) are physical or virtual machines? If virtual – are they on a different machine to the Windows 10 PC which you are connecting to? Are the mentioned hosts used only as a client or are you connecting to them via NoMachine at the same time? In other words, we need to know where each of the NoMachine installations are in relation to each other and whether they are being used as clients or servers.

Did you tried to change audio settings on server machine? Which devices are set as default on Playback and Recording panel? Is there difference if you uncheck “Listen to this device” in the recording device preferences?

[kroy]

Please try the solution from topic: https://www.nomachine.com/forums/topic/opensuse-leap-unable-to-authenticate-for-software-update#post-12181

[kroy]

As a temporary workaround you can download correctly org.freedesktop.packagekit.policy (newest is PackageKit-1.1.3) and replace with it your currently file. You can do it using following commands.

wget https://www.freedesktop.org/software/PackageKit/releases/PackageKit-1.1.3.tar.xz
tar xf PackageKit-1.1.3.tar.xz
sudo cp PackageKit-1.1.3/policy/org.freedesktop.packagekit.policy /usr/share/polkit-1/actions/

After that please logout and login to the desktop

[kroy]

Unfortunately, there is no any crash in the logs. Can you check if you have some crash report or core files (generated when issue had happen) in your home directory or in the /var/crash folder?

We still weren’t able to reproduce problem. Have you tried reversing sides? Does the problem appear also if you connect from Ubuntu 16 to Ubuntu 14?

[kroy]

At the moment we do not support KDE5 Plasma on Slackware. So for a workaround use xfce4 (add line DefaultDesktopCommand “/usr/bin/startxfce4” to /usr/NX/etc/node.cfg) or downgrade KDE.

[Author]

Posts