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

This is honestly borderline malware. Installing it makes kernel-level system startup modifications without notification. It broke my mouse4 and mouse5 buttons entirely. There's a script to uninstall the hooks, but this is dangerous to run because it appears to crash the entire kernel. It's also useless, because uninstalling the package itself automatically reinstalls all the hooks, right before removing everything they refer to and leaving your system GUI unbootable.

Thankfully it doesn't also make the CLI unbootable, though I'm suspicious this was an oversight and they'll take care of that in a future revision.

If you do make the mistake of installing this package . . . well, sorry, you're probably here because you're trying to figure out how to recover your system. But anyway, boot into a commandline prompt, remove this package, then visit https://bbs.archlinux.org/viewtopic.php?pid=2153377#p2153377 on your smartphone, and manually fix up all the files mentioned; /usr/share/sddm/scripts/Xsetup needs to be either modified by hand or restored from backup, all the others can just be deleted.

This desperately needs some polish.

Just so people know that this version has some major issues atm.

Things that did work in 8.10 but not in 8.11 (according to reports)

1) Intel Quicksync HW encode detection - (no amount of symlinking or install of older encode files fixes this)

2) Audio does not pass-through - for many users of Arch and even other distributions.

FYI: When uninstalling NoMachine, certain file changes appear not to be undone, see: https://bbs.archlinux.org/viewtopic.php?pid=2153377#p2153377. This can lead to Wayland acting up as well as other graphical issues.

@Cebtenzzre thanks for the info, I'll change mine accordingly.

@galvez_65 When you create an override unit (systemctl edit) without --full, systemd effectively appends the content to the existing unit. And according to the documentation for After/Before:

These two settings expect a space-separated list of unit names. They may be specified more than once, in which case dependencies for all listed names are created.

Which can be seen in practice if you systemctl show nxserver and look at the effective After= directive. In other words, there is no need to specify the other dependencies twice.

@Cebtenzzre thanks for posting this, I've had the same issues with nomachine hanging on shutdown as well. Rather than replace the After clause I added dbus.service systemd-logind.service to the end if it so mine now reads:

[Unit]
After = syslog.target network.target network-online.target sshd.service http-daemon.target.service htd.service dbus.service systemd-logind.service

I'm getting same issues as Ataraxy, furthermore it also appears to be setting an environment variable that prints in the terminal every time I try and do anything. This is the error message that is spammed

ERROR: ld.so: object '/usr/NX/lib/libnxegl.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

I fixed it by exporting a blank LD_PRELOAD, but still no usable nomachine

The nxserver unit hangs at shutdown without this systemd unit override:

# /etc/systemd/system/nxserver.service.d/override.conf
[Unit]
After=dbus.service systemd-logind.service

Is there a good way to automatically add this at install time until this is fixed upstream? I already reported the issue via their online form.

Doesn't pass pacman check that all owned files are installed (even after reinstall):

% sudo pacman -Qk nomachine                                                                      125ms | 23-10-04 13:53:14
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/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/nxrunner.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

@lucafs - I can concur, trying to connect wayland to wayland with KDE is broken, I get a white screen and it keeps dropping the connection. Wayland to x11 still works

Looks like it may be a known issue, hopefully the next release will fix it. (https://forum.nomachine.com/topic/blank-white-screen-kde-wayland-amd)