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.51
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 .. 5 6 7 8 9 10 11 12 13 14 15 .. 25 Next › Last »

G4Zz0L1 commented on 2020-12-09 16:41 (UTC)

Anyone has problems with starting the nx node in the latest version? I've tested on cinnamon and gnome, nxserver.service can't start the node in either DE, and the server hangs in place.

cdknight commented on 2020-10-23 15:07 (UTC)

On KDE 5.20.1 and NoMachine has been failing to work for me consistently for the past one month or so. Running it from the command line makes it immediately segfault. Removing the directory ~/.nx makes Nomachine take longer to segfault, but it still segfaults. Interestingly enough, on another Arch system that runs Awesome which is up-to-date, NoMachine starts just fine. This is probably a NoMachine problem, so I should probably ask elsewhere, but is anyone else having the same issue?

galvez_65 commented on 2020-10-18 21:05 (UTC) (edited on 2020-12-09 19:12 (UTC) by galvez_65)

Update: my issue seems resolved with 3.38.2, not sure what the issue was but it just started working again after the recent updates

Any one having issues with nomachine connecting to the display with gnome and wayland? Since the gnome update to 3.38 nomachine has not worked for me with wayland.

hcjl commented on 2020-10-05 18:51 (UTC)

@runnytu, enjoy your holiday. That's more important in these days... and in general ;-) Cheers

taek commented on 2020-10-05 18:18 (UTC) (edited on 2020-10-06 02:56 (UTC) by taek)

Updated PKGBUILD and uploaded it to my github.

please update this AUR repo! https://github.com/Taekus/nomachine

runnytu commented on 2020-10-05 17:51 (UTC)

I'm on holidays without a pc access until 13/10/2020, until then no update availability.

blackhole commented on 2020-10-05 17:18 (UTC)

When this will be updated?

Le_Birlante commented on 2020-10-04 23:26 (UTC)

Confirmed 6.12.3_5 ARMv7l working flawlessly on RPI4, 5.4.69-1-ARCH.

regards,

dec commented on 2020-10-03 20:20 (UTC)

Hi runnytu, could be that something is wrong with nomachine_6.11.2_1_x86_64.tar.gz. My systems tells me that the sha512sums checksum is wrong.

chema commented on 2020-10-02 07:21 (UTC)

@lateparty

Thank you very much. I will try it.