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.53
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 2 3 4 5 6 7 8 .. 25 Next › Last »

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:

[Unit]
After = syslog.target network.target network-online.target sshd.service http-daemon.target.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: ld.so: object '/usr/NX/lib/libnxegl.so' 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

Cebtenzzre commented on 2024-02-18 19:40 (UTC)

The nxserver unit hangs at shutdown without this systemd unit override:

# /etc/systemd/system/nxserver.service.d/override.conf
[Unit]
After=dbus.service systemd-logind.service

Is there a good way to automatically add this at install time until this is fixed upstream? I already reported the issue via their online form.

Ataraxy commented on 2023-10-04 06:54 (UTC)

Doesn't pass pacman check that all owned files are installed (even after reinstall):

% sudo pacman -Qk nomachine                                                                      125ms | 23-10-04 13:53:14
warning: nomachine: /usr/NX/etc/NX/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/localhost/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/localhost/server.cfg.sample (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxnode.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxplayer.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxrunner.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxserver.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/nxserver (No such file or directory)
nomachine: 13 total files, 10 missing files

galvez_65 commented on 2023-08-22 16:37 (UTC) (edited on 2023-08-22 16:40 (UTC) by galvez_65)

@lucafs - I can concur, trying to connect wayland to wayland with KDE is broken, I get a white screen and it keeps dropping the connection. Wayland to x11 still works

Looks like it may be a known issue, hopefully the next release will fix it. (https://forum.nomachine.com/topic/blank-white-screen-kde-wayland-amd)

lucasf commented on 2023-08-21 21:15 (UTC)

I can't connect with Wayland but I can connect with X11, both in Gnome and KDE. Has anyone else had that problem?

Adramyttium commented on 2023-07-29 15:10 (UTC)

@runnytu I had a build problem on my end and mistakenly attributed it to the package being out of date. I was totally wrong. I apologize.

fang64 commented on 2023-07-26 01:33 (UTC)

I've email you another update patch to get to 8.8.1_1 of nomachine.


From 6d5087ca8180dbfdcf98bab487aad423fcd3490e Mon Sep 17 00:00:00 2001
From: fang64 <fang64@gmail.com>
Date: Tue, 25 Jul 2023 21:24:27 -0400
Subject: [PATCH] Update to 8.8.1

---
 PKGBUILD | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index 8c2a818..03cb352 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -11,8 +11,8 @@ _autofirewall=n
 ### END BUILD OPTIONS

 pkgname=nomachine
-pkgver=8.7.1
-_pkgvermain=8.7
+pkgver=8.8.1
+_pkgvermain=8.8
 _pkgrel_i686=1
 _pkgrel_x86_64=1
 _pkgrel_armv6h=1
@@ -30,13 +30,13 @@ options=('!strip')
 conflicts=('nxmanager' 'nxwebplayer' 'nxserver' 'nxnode' 'nxclient')
 depends=('bash' 'openssh' 'nawk' 'polkit' 'rpm-tools' 'dkms')
 optdepends=('xorg-xauth: allows logging into a headless machine')
-sha512sums_x86_64=('6ddd39d9ab3f27ccc0d926251ee12466724287d896f0303d30fd3145c7e8829f45aa5a60760b0a70e5936d7b19182b814ddb572b0f44fb17e283ef11ce2d1942')
-sha512sums_i686=('87363071003d05dc760a8b1dbfc556d4b0162d40df7f20266ea9a27daeed33e2f3f7b788ba596e143f2096479253f2b8cc477191da2363a6d9266ed25bbb98c9')
-sha512sums_armv6h=('27f3ccf5cab98ea29763c0af6de31139bb0880ad7ae1b462ad407f8069234576aff68bbc57d511c19cc3920001fed473f1a0db0f5b1d121e229be09f00e71411')
-sha512sums_armv7h=('7763f3b00317a5db74e9c8145b473f28f5f6b5dea8df2ddaeba99364a0355eaa666681e325eef5e8fca442932c7c5e999d5b90cb523a2c6e7dba091a79cc9f02')
-sha512sums_armv8h=('6713afa635a3488c90f10d9d0e6ef876e1913801138bc4431a15d4fdea30eac30d23acff0639d8c3c786f954d391d019921cdfa72f90299cca2c841cd7210a8f')
-sha512sums_aarch64=('6713afa635a3488c90f10d9d0e6ef876e1913801138bc4431a15d4fdea30eac30d23acff0639d8c3c786f954d391d019921cdfa72f90299cca2c841cd7210a8f')
-sha512sums_pentium4=('87363071003d05dc760a8b1dbfc556d4b0162d40df7f20266ea9a27daeed33e2f3f7b788ba596e143f2096479253f2b8cc477191da2363a6d9266ed25bbb98c9')
+sha512sums_x86_64=('b2cf90e300d6c510a1e66d32fa8f8f894300a25259418fb801a5b53eeef36867643ca78836ad3287a2da80c374090049257ee0a148b6e80a77267d81b9d89d5a')
+sha512sums_i686=('930faae1a785c68fa61a0cb3b970aadc72ea949f38509ab8fa00461689300dcac0e5d2a279427689436a0eecd2ff693c8fa47ccccb0b160b78566ca3295e2746')
+sha512sums_armv6h=('705b4dd7841a3c788af77f9fb4ce9d2f247968a582b06833996984997dd32ca582c05d92f3cbf71a055ef9f19682c17837151e0e540c2db6037eee793f94052e')
+sha512sums_armv7h=('321bb92913ce93907c4b8af74aab89b245ee7225ca7651e383e256a53a8ee54a1d67d853b8258b27a6ad56871b7231c456e33e1d84d9866fdc703b2c88032803')
+sha512sums_armv8h=('15c905ba4127c71c8a44b4cfcf30f9a7686f583275b0c2692ae7e5d98053ffd2e88808876eaa3a291c218196542c8a41c4411e3cc0abf05262ffaec81eab452b')
+sha512sums_aarch64=('15c905ba4127c71c8a44b4cfcf30f9a7686f583275b0c2692ae7e5d98053ffd2e88808876eaa3a291c218196542c8a41c4411e3cc0abf05262ffaec81eab452b')
+sha512sums_pentium4=('930faae1a785c68fa61a0cb3b970aadc72ea949f38509ab8fa00461689300dcac0e5d2a279427689436a0eecd2ff693c8fa47ccccb0b160b78566ca3295e2746')
 source_x86_64=("http://download.nomachine.com/download/${_pkgvermain}/Linux/${pkgname}_${pkgver}_${_pkgrel_x86_64}_x86_64.tar.gz")
 source_i686=("http://download.nomachine.com/download/${_pkgvermain}/Linux/${pkgname}_${pkgver}_${_pkgrel_i686}_i686.tar.gz")
 source_armv6h=("http://download.nomachine.com/download/${_pkgvermain}/Raspberry/${pkgname}_${pkgver}_${_pkgrel_armv6h}_armv6hl.tar.gz")
-- 
2.41.0

I've tested it seems to work on both platforms.

runnytu commented on 2023-06-17 12:10 (UTC)

@Adramyttium, stop marking out of date the package, it is the last version for a while.

Funkin-Stoopid commented on 2023-06-13 00:05 (UTC) (edited on 2023-06-17 13:36 (UTC) by Funkin-Stoopid)

Hello Since 8.5.3 update, I have no more sound through nomachine.