Package Details: nomachine 8.16.1-1

Git Clone URL: https://aur.archlinux.org/nomachine.git (read-only, click to copy)
Package Base: nomachine
Description: Remote desktop application
Upstream URL: http://www.nomachine.com
Licenses: custom:"NoMachine EULA"
Groups: network
Conflicts: nxclient, nxmanager, nxnode, nxserver, nxwebplayer
Submitter: FreeK
Maintainer: runnytu
Last Packager: runnytu
Votes: 95
Popularity: 0.22
First Submitted: 2014-07-24 15:45 (UTC)
Last Updated: 2025-02-01 20:34 (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:

BUILD OPTIONS
Set to y to enable nomachine service autostart

_autoservice=n

Set to y to enable firewall autorules

_autofirewall=n

END BUILD OPTIONS

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 25 Next › Last »

galvez_65 commented on 2021-02-15 17:08 (UTC) (edited on 2021-02-15 23:31 (UTC) by galvez_65)

This may be caused by not updating correctly. I edited nomachine.install removing the pre_upgrade stanza and changed the post_upgrade stanza to be:


post_upgrade() {
    echo "Running NX update script..."
    /usr/NX/nxserver --update fedora
}

which seems to fix the issue. I'm not sure why --uninstall and --install are used rather than --update so there may be other unintended consequences, but unless there is a reason I would suggest or at least explore changing the upgrade procedure.

blackhole commented on 2021-02-15 11:13 (UTC)

With the last versions nomachine will start correctly only if removed completely first explicitly

galvez_65 commented on 2021-02-10 23:31 (UTC)

@Groumpf I can confirm I had to do the same thing to attach to my wayland session on gnome as well

Groumpf commented on 2021-02-10 20:02 (UTC) (edited on 2021-02-13 15:00 (UTC) by Groumpf)

For people upgrading to 7.1.3, I had to do this to recover the ability to attach to a running X session.

sudo /etc/NX/nxserver --addtoredis
sudo systemctl restart nxserver

Not sure if it's something that should make it into the PKGBUILD or if it's a hiccup with upgrading.

torma commented on 2021-01-08 05:37 (UTC)

Is anybody else having trouble getting the nxserver to start? I'm getting errors that there is no valid subscription files.

blackhole commented on 2020-12-26 14:18 (UTC)

SOLVED removing completely nomachine, checking that all files was removed, deleting yay cache and reinstalling

blackhole commented on 2020-12-25 21:55 (UTC)

With last version I cannot connect any more to a lxqt desktop.

anupamsr commented on 2020-12-23 19:33 (UTC)

The package has been upgraded to 7.0.211 and the download links don't seem to work any more.

skiwi commented on 2020-12-23 15:40 (UTC)

Package seems to miss the sha keys (installed via yay)

==> Making package: nomachine 7.0-1 (Wed 23 Dec 2020 04:20:50 PM CET) ==> Retrieving sources... -> Found nomachine_7.0.209_9_x86_64.tar.gz ==> Validating source_x86_64 files with sha512sums... nomachine_7.0.209_9_x86_64.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check! error downloading sources: nomachine

blackhole commented on 2020-12-23 13:05 (UTC)

Right mouse click on tray icon does not show saved connections any more. I need to restore main window first.