Package Details: nomachine 6.7.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: 61
Popularity: 0.950591
First Submitted: 2014-07-24 15:45
Last Updated: 2019-05-25 12:23

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

runnytu commented on 2017-01-05 20:56

@blackhole, startlxqt isn't the correct command, it should /usr/bin/lxqt-session with perhaps some option more.

blackhole commented on 2017-01-05 11:33

I have this problem:

Maybe this version cannot launch my already installed remote Desktop if system is in

czk commented on 2016-11-29 01:03


Much appreciated. I will give that a whirl on the next nomachine upgrade.

runnytu commented on 2016-11-28 23:03

@czk, I fixed the Fedora variable error, equally nomachine was working ok even with the error, furthermore i added two options, first one to disable the service autostart and the second to disable the automatic firewall rules, only is necesary to edit the PKGBUILD file, and change the _autoservice and _autofirewall variables in the begin of the PKGBUILD and continue with the build process, i don't change the package version to avoid users that don't want to change the autostart options, they don't have need to reinstall the package.

czk commented on 2016-11-26 11:05

machine.install runs `/usr/NX/nxserver --install fedora`. This results in an error I noticed during upgrade from 5.1.54-1 to 5.1.62-1:

/usr/NX/scripts/setup/nxclient: line 4243: [: -ge: integer expression expected
That's because `majorFedoraVersion` var won't get set on non-Fedora systems. I haven't verified whether this leads to any problems. Not using NX much recently. @runnytu, can you please check this out?

I have also rembered 2 other security issues besides the firewall problem I described on 2016-10-24: this software will enable and start the nxserver.service on your machine.

Auto-starting and auto-enabling a service, let alone a network service, and punching holes in host's firewall is a practice hard to accept. Please do someting about this before the next package release. It is a great piece of software and kudos for maintaing it, yet this issues are too serious to be ignored. Auto-starting the client app after the installation doesn't look OK either.

runnytu commented on 2016-11-23 20:46

Hello, Bump to new version 5.1.62-1, added ssh dependency.

czk commented on 2016-10-24 08:57

NX is no doubt a great piece of software. But it has the following issues the users should be aware of:

- nxserver.service opens TCP 4000 port to incoming connections without asking, even if you have your firewall set-up to block all incoming connections. And it will close the port back on NX service termination, again without letting the user control this. If you want to be able to manage the firewall yourself, edit lines 84 and 87 in /usr/NX/scripts/restricted/ to your liking. I simply commented them out.

- It forces sshd.service start on your machine, due to "Wants=sshd.service" in /usr/lib/systemd/system/nxserver.service. I guess this also means that the nomachine package should require opnssh package explicitely.

runnytu commented on 2016-10-01 14:46

Hello, Bump to new version 5.1.54-1, added armv8h arch too.

runnytu commented on 2016-08-04 18:35

Hello, Bump to new version 5.1.44-1.

runnytu commented on 2016-07-27 18:20

Hello, Bump to new version 5.1.42-1.