Package Details: nomachine 8.11.3-1

Git Clone URL: (read-only, click to copy)
Package Base: nomachine
Description: Remote desktop application
Upstream URL:
Licenses: custom:"NoMachine EULA"
Groups: network
Conflicts: nxclient, nxmanager, nxnode, nxserver, nxwebplayer
Submitter: FreeK
Maintainer: runnytu
Last Packager: runnytu
Votes: 91
Popularity: 0.71
First Submitted: 2014-07-24 15:45 (UTC)
Last Updated: 2024-02-05 20:30 (UTC)

Pinned Comments

runnytu commented on 2021-02-20 13:44 (UTC)

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:

Set to y to enable nomachine service autostart


Set to y to enable firewall autorules



Latest Comments

1 2 3 4 5 6 .. 24 Next › Last »

fex0r commented on 2024-05-15 20:49 (UTC)

Uninstalling this package completely broke my Plasma-6 desktop. However, thanks to I was able to resolve the issue.


sudo rm -rf /etc/udev/rules.d/99-virtualgl-dri.rules
sudo rm -rf /etc/opt/VirtualGL
sudo rm -rf /usr/share/sddm/scripts/Xsetup
sudo rm -rf /usr/share/gdm/greeter/autostart/virtualgl.desktop
sudo rm -rf /etc/modprobe.d/virtualgl.conf
sudo rm -rf /etc/X11/xorg.conf.d/99-virtualgl-dri

For removing configuration files that were not fully cleared during the uninstallation process.

ls -l /dev/dri/
getfacl /dev/dri/renderD128

If there is any mention of 'vglusers', it indicates that the cleanup might not have been fully successful.

consularbtw commented on 2024-04-28 16:37 (UTC)

Hello, I have been trying to install the latest version of the package using yay and have ran into some issues. The remote desktop windows do not open, which I have figured is due to nvidia driver being used for hardware encoding but due to permission issues in the /etc/NX directory, I am unable to change any settings of the app which makes it completely unusable at the moment. Whenever I click to change some setting, it asks for administrator authorization which ultimately fails even if given the correct password. I have tried fixes from the nomachine forum but the issue persists.

dgk commented on 2024-04-19 23:26 (UTC)

after pamac build nomachine

see sudo /usr/NX/bin/nxserver --status

there is an issue where nxd service is set to manual start instead of automatic so upon starting of nxserver systemd service you can't connect because nxd (a nomachine service) has not started. You can fix that in the UI but via cli

run sudo /usr/NX/bin/nxserver --startmode nxd automatic

then for current session sudo /usr/NX/bin/nxserver --restart nxd

not sure if this is an ommission in the build script or not but it's always the same on every machine I install this build on.

zorbathut commented on 2024-04-06 22:13 (UTC) (edited on 2024-04-06 22:13 (UTC) by zorbathut)

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 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.

theriddick commented on 2024-03-09 04:59 (UTC) (edited on 2024-04-02 07:49 (UTC) by theriddick)

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.

STEELBAS commented on 2024-02-26 22:12 (UTC)

FYI: When uninstalling NoMachine, certain file changes appear not to be undone, see: This can lead to Wayland acting up as well as other graphical issues.

galvez_65 commented on 2024-02-19 17:13 (UTC)

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

Cebtenzzre commented on 2024-02-19 15:15 (UTC) (edited on 2024-02-19 15:16 (UTC) by Cebtenzzre)

@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.

galvez_65 commented on 2024-02-19 13:48 (UTC) (edited on 2024-02-19 13:50 (UTC) by galvez_65)

@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:

After = sshd.service htd.service dbus.service systemd-logind.service

symo521 commented on 2024-02-19 00:39 (UTC)

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: object '/usr/NX/lib/' 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