Package Details: nomachine 8.14.2-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: 92
Popularity: 0.41
First Submitted: 2014-07-24 15:45 (UTC)
Last Updated: 2024-10-04 19:35 (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

1 2 3 4 5 6 .. 25 Next › Last »

polpoman commented on 2024-11-17 14:28 (UTC)

Does audio passthrough work for anybody here? I use KDE + X11, and it doesn't for me.

mfcmquintela commented on 2024-10-28 15:48 (UTC)

@galvez_65 had to test it because i'm having a very weird bug with kde in x11 and one of my monitors (apparently it's monitor related). wanted to test wayland, but considering i'm unable to use nomachine on my desktop (nvidia btw lol) i'll have to keep dealing with the dumb x11 bug. i'll keep an eye here in case you get an answer :)

galvez_65 commented on 2024-10-28 12:43 (UTC)

@mfcmquintela I'm having the same issue white screen and timing out, I opened a ticket on the !M forum. Hopefuly it's something simple.

galvez_65 commented on 2024-10-22 22:35 (UTC)

@mfcmquintela I have it working on at one of my machines but not another and but are running wayland. I've not had time to troubleshoot why the second one isn't working,

mfcmquintela commented on 2024-10-22 14:33 (UTC)

@galvez_65 have you managed to get nomachine working on Wayland with Plasma6? I'm currently getting the same error as reported in their website: https://forum.nomachine.com/topic/plasma-6-wayland-connection-issue-104-error/page/2 , https://kb.nomachine.com/TR05V11141?s=wayland

galvez_65 commented on 2024-10-04 15:42 (UTC) (edited on 2024-10-04 15:45 (UTC) by galvez_65)

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")

galvez_65 commented on 2024-07-19 17:44 (UTC) (edited on 2024-10-03 20:31 (UTC) by galvez_65)

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

fex0r commented on 2024-05-15 20:49 (UTC)

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.

consularbtw commented on 2024-04-28 16:37 (UTC)

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.

dgk commented on 2024-04-19 23:26 (UTC)

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.