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

Hi, Thank you for keeping this package up to date. Where can I find info on the new dependencies ('polkit' 'rpm-tools' 'dkms')? I quick look through the Nomachine isn't bringing anything up. Thanks

Missing dependency: linux-headers

nxusb won't build without it and USB Device Pass-through functionality will not work.

@jholmer, read the pinned comment.

I had trouble getting this to work initially on a headless server. I found out the issue was that systemctl start nxserver did not start nxd and I had to manually sudo /etc/NX/nxserver --restart to get it to start. I'm not sure if this is something that needs to/should be fixed in this package?

Regarding the segfault mentioned by blackhole and aag, the following threads seem to contain further information:

• https://forums.nomachine.com/topic/manjaro-ubuntu-connection-problem
• https://forums.nomachine.com/topic/nomachine-client-disconnects-right-after-connection-in-latest-manjaro
• https://bugzilla.mozilla.org/show_bug.cgi?id=1758473

Either revert libva to 2.14.0-1 as mentioned by aag, or set '<option key="Enable hardware accelerated decoding" value="disabled" />' in ~/.nx/config/player.cfg as mentioned in the nomachine forum threads.

Setting the above to "false" seems to have the same impact as "true", while "disabled" works. Bizarre.

Same segfault here

Getting a segfault in client with libva-2.15.0-1:

nxplayer.bin[5918]: segfault at d8 ip 00007f736444eff0 sp 00007f73517fa2e8 error 4 in libnxdixl.so[7f7364400000+cc000]

reverting it to 2.14.0-1 fixes the problem for me.

There are quite a few things that probably should be looked into in this package.

1. The postinst should be created in an appropriate environment before the package is created, not after it is created. If nxserver can't handle that, the postinst steps should be performed manually.
2. The postinst should not start or enable nxserver, this should be left up to the user. Starting and enabling services isn't an appropriate thing to do in a postinst.
3. Packaged files are removed after packaging, which means pacman -Qk fails.
4. The installer isn't given the appropriate XDG environment, so it creates a root directory, /applications-merged:

% ls -l /applications-merged
total 4
-rw-r--r-- 1 root root 593 Apr 13 14:18 NoMachine-dir.menu

Just a FYI. If your session terminates/crashes instead of locking it might be caused by this

https://knowledgebase.nomachine.com/TR02T10468

I had screen blacking enabled in nxserver settings and currently it seems to crash Xorg on session switch/lock.

% sudo pacman -Qk nomachine
warning: nomachine: /usr/NX/etc/NX/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/localhost/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/localhost/server.cfg.sample (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxclient.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxnode.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxplayer.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxserver.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/nxserver (No such file or directory)
nomachine: 13 total files, 10 missing files