Arch Linux User Repository

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

here is a patch for 8.14.2 if anyone is interested

--- a/PKGBUILD
+++ b/PKGBUILD
@@ -11,8 +11,8 @@
 ### END BUILD OPTIONS

 pkgname=nomachine
-pkgver=8.13.1
-_pkgvermain=8.13
+pkgver=8.14.2
+_pkgvermain=8.14
 _pkgrel_i686=1
 _pkgrel_x86_64=1
 _pkgrel_armv6h=1
@@ -30,13 +30,13 @@
 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=('6f6e6b1297ff3551d121978e46807b97f379829157d5878d4267b527e9369f7de402fe0d7827b2a8ec3c7e3d693a7bb6d6bb8dd9733e5f4bd4b2f30fae55cc30')
-sha512sums_i686=('bca989b6116090d76c5279e7f6952b1042ba0a34d5bb1eed581668c4f248ac4856a3eac1b2e50aed5c0df4f3b911716f3b28cc863ba9e74922c68b390c76d7d0')
-sha512sums_armv6h=('3993e6b1c2708e521c7aac7464be2e3d5c161f1a6807f507ae1e6159855dfbf652ef26340457e9873965cd85f1bf871a9f83c95f33717b01f9b80683f4fa7298')
-sha512sums_armv7h=('6cfbd30838e40065244266fb71397e3ef9662a064c5da3a97abdf1f9bbae91e803591c41bd5fb09c7dec9e409a9a55fa5d14837491e630f0d9637fb4ba5de448')
-sha512sums_armv8h=('77938cf21bfb29afb188acf56f3e6710ebf982729344fdef853d6ae28370636a5c4e18b99b5ca0748d741a6a42fcfeeb7502dea4895f002d383cd5005c834a00')
-sha512sums_aarch64=('77938cf21bfb29afb188acf56f3e6710ebf982729344fdef853d6ae28370636a5c4e18b99b5ca0748d741a6a42fcfeeb7502dea4895f002d383cd5005c834a00')
-sha512sums_pentium4=('bca989b6116090d76c5279e7f6952b1042ba0a34d5bb1eed581668c4f248ac4856a3eac1b2e50aed5c0df4f3b911716f3b28cc863ba9e74922c68b390c76d7d0')
+sha512sums_x86_64=('c3bf7e045b21811e9915d504a40a76214772393c3ac43944f62966337b739a80585217c93755509a4851528d47c34dfd796709a7090ffa8c69cc98148ef92988')
+sha512sums_i686=('286e2927fcca9f74bf4dc9809192d08274b00058190e87ea3f69f6fdfa0d981ec07766d6a896141e840ab182ea4fbc296bdf30a0621bf1a0521b75a9837f9fbf')
+sha512sums_armv6h=('1c1e70e9912d9b3e1c87bdaab5974072b0d3f49a9c1258ca0821441ebe92baf83c858242fe2f1c12b9f8daaba627ab59ee91bfd6baab9bd8da344052c9ac43d4')
+sha512sums_armv7h=('5efaa4e87d371ca4c83eeaffeefcc7d3dff628995af80fbdebce68dfeace9a8ce395f5b4ef71784e2523bd755b6871078d21604d29188fea5ed99b063850d2dd')
+sha512sums_armv8h=('ac8584028692974405fae69e46e55c625b46a43e1c054a690a04fedeeea7fbeb928eeecd54810c563132fc5fca15a75cdf1e8e512a4c29554839fe9e665eeda6')
+sha512sums_aarch64=('ac8584028692974405fae69e46e55c625b46a43e1c054a690a04fedeeea7fbeb928eeecd54810c563132fc5fca15a75cdf1e8e512a4c29554839fe9e665eeda6')
+sha512sums_pentium4=('286e2927fcca9f74bf4dc9809192d08274b00058190e87ea3f69f6fdfa0d981ec07766d6a896141e840ab182ea4fbc296bdf30a0621bf1a0521b75a9837f9fbf')
 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")

If anyone is able to get !M to work with KDE on Wayland I would appreciate to hear how you git it to work. I have not been able to get !M tow work with Wayland since Plasma6 update. Supposedly it should work with version 8.12.12, but I am still getting 104 white screen errors. I've posted the the !M forum and will post back here is this gets solved, but also wanted to cross-post here in case someone has a viable workaround that isn't "use X"

Update looks like this is fixed with the 8.14.2 release

Uninstalling this package completely broke my Plasma-6 desktop. However, thanks to https://bbs.archlinux.org/viewtopic.php?pid=2153377#p2153377 I was able to resolve the issue.

TLDR;

sudo rm -rf /etc/udev/rules.d/99-virtualgl-dri.rules
sudo rm -rf /etc/opt/VirtualGL
sudo rm -rf /usr/share/sddm/scripts/Xsetup
sudo rm -rf /usr/share/gdm/greeter/autostart/virtualgl.desktop
sudo rm -rf /etc/modprobe.d/virtualgl.conf
sudo rm -rf /etc/X11/xorg.conf.d/99-virtualgl-dri

For removing configuration files that were not fully cleared during the uninstallation process.

ls -l /dev/dri/
getfacl /dev/dri/renderD128

If there is any mention of 'vglusers', it indicates that the cleanup might not have been fully successful.

Hello, I have been trying to install the latest version of the package using yay and have ran into some issues. The remote desktop windows do not open, which I have figured is due to nvidia driver being used for hardware encoding but due to permission issues in the /etc/NX directory, I am unable to change any settings of the app which makes it completely unusable at the moment. Whenever I click to change some setting, it asks for administrator authorization which ultimately fails even if given the correct password. I have tried fixes from the nomachine forum but the issue persists.

after pamac build nomachine

see sudo /usr/NX/bin/nxserver --status

there is an issue where nxd service is set to manual start instead of automatic so upon starting of nxserver systemd service you can't connect because nxd (a nomachine service) has not started. You can fix that in the UI but via cli

run sudo /usr/NX/bin/nxserver --startmode nxd automatic

then for current session sudo /usr/NX/bin/nxserver --restart nxd

not sure if this is an ommission in the build script or not but it's always the same on every machine I install this build on.

This is honestly borderline malware. Installing it makes kernel-level system startup modifications without notification. It broke my mouse4 and mouse5 buttons entirely. There's a script to uninstall the hooks, but this is dangerous to run because it appears to crash the entire kernel. It's also useless, because uninstalling the package itself automatically reinstalls all the hooks, right before removing everything they refer to and leaving your system GUI unbootable.

Thankfully it doesn't also make the CLI unbootable, though I'm suspicious this was an oversight and they'll take care of that in a future revision.

If you do make the mistake of installing this package . . . well, sorry, you're probably here because you're trying to figure out how to recover your system. But anyway, boot into a commandline prompt, remove this package, then visit https://bbs.archlinux.org/viewtopic.php?pid=2153377#p2153377 on your smartphone, and manually fix up all the files mentioned; /usr/share/sddm/scripts/Xsetup needs to be either modified by hand or restored from backup, all the others can just be deleted.

This desperately needs some polish.

Just so people know that this version has some major issues atm.

Things that did work in 8.10 but not in 8.11 (according to reports)

1) Intel Quicksync HW encode detection - (no amount of symlinking or install of older encode files fixes this)

2) Audio does not pass-through - for many users of Arch and even other distributions.

FYI: When uninstalling NoMachine, certain file changes appear not to be undone, see: https://bbs.archlinux.org/viewtopic.php?pid=2153377#p2153377. This can lead to Wayland acting up as well as other graphical issues.

@Cebtenzzre thanks for the info, I'll change mine accordingly.

@galvez_65 When you create an override unit (systemctl edit) without --full, systemd effectively appends the content to the existing unit. And according to the documentation for After/Before:

These two settings expect a space-separated list of unit names. They may be specified more than once, in which case dependencies for all listed names are created.

Which can be seen in practice if you systemctl show nxserver and look at the effective After= directive. In other words, there is no need to specify the other dependencies twice.