Arch Linux User Repository

Since nomachine 7.1.3-2 the default behavior of the package is StartNXDaemon Manual and FirewallConfiguration 0 on a new installation, if you want to change this, you need to modify PKGBUILD build options with your desire behavior:

BUILD OPTIONS

Set to y to enable nomachine service autostart

_autoservice=n

Set to y to enable firewall autorules

_autofirewall=n

END BUILD OPTIONS

checksums failing for anyone else?

I don't know if this is a joke or not. Just go search through settings, man.

Does anyone know how to configure this to use a different port than the default 4000?

Anyone having issues connecting to a server running GDM? with GDM 3.36 if I try to remote into a machine which I am not already logged into I get a white screen. If I am physically logged in I can remote in without issue. Rolling GDM back to 3.34 resolved the issue for me.

I am getting:

==> Validating source_x86_64 files with sha512sums... nomachine_6.9.2_1_x86_64.tar.gz ... FAILED

@Le_Birlante, I have exactly the same problem (RPI4, Archlinux ARM, XFCE). So unfortunately just a confirmation, not a solution :-(

Hi there,

I think this is upstream territory, but anyway, here it goes in case someone here could confirm this one.

Scenario : Raspberry PI 4 running Arch Linux for ARM, KDE+Plasma, NoMachine 6.9.2 package. Eeverything runs flawlessly for weeks, not even a single problem.

The problem: latest arch/arm kernel updates (over the past week there have been two linux-raspberrypi4 updates, latest is 4.5.35-1) seem to have broken NoMachine. It will simply refuse to start.

If you go to nxserver.log, you can see NX is trying to get an instance up and running, but to no avail:

2020-05-04 22:58:09 254.556 21823 NXSERVER WARNING! Process '/usr/NX/bin/nxexec --node --user xxx --priority realtime --mode 0 --pid 16' with pid '23454/23454' finished with exit code 127 after 1,453 seconds. 2020-05-04 22:58:09 255.262 21823 NXSERVER WARNING! FBA3ED947BAD40D54C4D64B030FDC4BA nxnode died with exit code 127.

2020-05-04 22:58:09 372.189 21823 NXSERVER WARNING! Session FBA3ED947BAD40D54C4D64B030FDC4BA crashed on display 0.

2020-05-04 22:58:10 916.236 21823 NXSERVER WARNING! Process '/usr/NX/bin/nxexec --node --user xxx --priority realtime --mode 0 --pid 14' with pid '23601/23601' finished with exit code 127 after 1,528 seconds.

2020-05-04 22:58:10 916.821 21823 NXSERVER WARNING! AE162AD84888CEDA4DC8F1DB456033EB nxnode died with exit code 127.

2020-05-04 22:58:11 007.321 21823 NXSERVER WARNING! Session AE162AD84888CEDA4DC8F1DB456033EB crashed on display 0.

I inspected one of those crashed sessions ( /usr/NX/var/log/node/F-C-session_hex_code_here/session ) and this is the only suspect I could see :

Session: Starting session at Mon May 4 22:58:16 2020. Info: Agent running with pid 24113. Info: Slave server running with pid 24186. Info: Display running with pid 24187. Info: Listening to slave connections on port 12003. Info: Audio client started with pid 24195. Info: Audio server started with pid 24194. Info: Display server started with pid 24196.

=======>>>>>> /usr/NX/bin/nxnode.bin: symbol lookup error: /usr/NX/lib/libnxdifb.so: undefined symbol: __pow_finite <<<<<<=====

Thing is, I am not sure whether the 'pow_finite' symbol failure was already present as a simple warning before the rpi4 kernel update, or whether it's indeed the culprit of NX crashing. Turns out, I had never before had to look at these logs, since everything was working ok, so perhaps the pow_finite thingie was always there and it has nothing to do with the current problem. Go figure...

Long story short: Nomachine for RPI4 is broken since two kernel updates ago (more or less a week ago, talking in days). If you use NX with your PI4 like me, try not to upgrade the kernel.

regards !

@smekkleysa, both are in the base package, that is the minimum you should have installed, and never are in the depends part of an aur package.

For super minimal setup, tar and hostname command are needed.

@runnytu Awesome, thank you!!