Package Details: nomachine 6.4.6-1

Git Clone URL: (read-only)
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: 56
Popularity: 2.452605
First Submitted: 2014-07-24 15:45
Last Updated: 2018-12-11 19:20

Latest Comments

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

marcin commented on 2018-08-03 01:03

FYI: This comes with nxplayer (/usr/NX/bin/nxplayer) which can be used to connect to nxservers. For some reason arch wiki on nx does not mention this and only says about nxclient.

brittyazel commented on 2018-06-18 15:52

The latest NoMachine isn't compatible with the version of ffmpeg in the main repos. As a result, h264 isn't working at all. I tested a couple of the ffmpeg-compat packages with no success. Any ideas?

update* Cool, installing the compat package and symlinking '/usr/lib/ > /usr/NX/lib/' and '/usr/lib/ > /usr/NX/lib/' worked like a charm.

runnytu commented on 2018-06-13 20:41

@mrfabjr, try again, it was outdated.

mrfabjr commented on 2018-06-13 13:43

Getting the following errors:

curl: (22) The requested URL returned error: 404 Not Found

==> ERROR: Failure while downloading Aborting... ==> ERROR: Makepkg was unable to build nomachine.

Tried installing using:


$ yaourt -S nomachine

I've done the following:

Updated system

Refreshed Databases

no luck.


runnytu commented on 2018-06-02 13:36

@meriops, fixed.

meriops commented on 2018-06-01 19:11

makepkg complains that the "conflict" entry contains illegal characters. This entry should be: conflicts=('nxmanager' 'nxwebplayer' 'nxserver' 'nxnode' 'nxclient') rather than the current:<br> conflicts=('nxmanager nxwebplayer nxserver nxnode nxclient')

kubrick commented on 2018-04-28 10:48

Hi, is there a way to fix this problem permanently please?

parkerlreed commented on 2018-02-15 17:22

Ahh cheers, missed that.

runnytu commented on 2018-02-14 20:41

@parkerlreed, there is an option in the PKGBUILD to disable nomachine service autostart, you only need to change it to no, also there is a banner during installation informing you "No Changes To Automatic Service Start And Firewall Automatic Rules" if you don't touch the variable.

@brittyazel, fixed.

parkerlreed commented on 2018-02-14 16:45

The post install command enables the service automatically...

Might want to make a note of this in the post install script in case the user installing it only wants to use it as a client.