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. => /usr/NX/bin/nxnode.bin: symbol lookup error: /usr/NX/lib/libnxdifb.so: undefined symbol: _pow_finite <<<<<<=

Info: Display server started with pid 24196. Info: Audio server started with pid 24194. Info: Audio client started with pid 24195. Info: Listening to slave connections on port 12003. Info: Slave server running with pid 24186. Session: Starting session at Mon May 4 22:58:16 2020. 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 : 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. 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. If you go to nxserver.log, you can see NX is trying to get an instance up and running, but to no avail:

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.

Eeverything runs flawlessly for weeks, not even a single problem. Scenario : Raspberry PI 4 running Arch Linux for ARM, KDE+Plasma, NoMachine 6.9.2 package. I think this is upstream territory, but anyway, here it goes in case someone here could confirm this one.

Install nomachine on raspberry pi 3