Package Details: nomachine 7.10.1-1

Git Clone URL: (read-only, click to copy)
Package Base: nomachine
Description: Remote desktop application
Upstream URL:
Licenses: custom:"NoMachine EULA"
Conflicts: nxclient, nxmanager, nxnode, nxserver, nxwebplayer
Submitter: FreeK
Maintainer: runnytu
Last Packager: runnytu
Votes: 82
Popularity: 0.082707
First Submitted: 2014-07-24 15:45 (UTC)
Last Updated: 2022-06-22 19:16 (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:

Set to y to enable nomachine service autostart


Set to y to enable firewall autorules



Latest Comments

cdown commented on 2022-04-13 22:33 (UTC) (edited on 2022-04-13 22:37 (UTC) by cdown)

There are quite a few things that probably should be looked into in this package.

  1. The postinst should be created in an appropriate environment before the package is created, not after it is created. If nxserver can't handle that, the postinst steps should be performed manually.
  2. The postinst should not start or enable nxserver, this should be left up to the user. Starting and enabling services isn't an appropriate thing to do in a postinst.
  3. Packaged files are removed after packaging, which means pacman -Qk fails.
  4. The installer isn't given the appropriate XDG environment, so it creates a root directory, /applications-merged:
% ls -l /applications-merged
total 4
-rw-r--r-- 1 root root 593 Apr 13 14:18

wereii commented on 2022-02-16 23:24 (UTC)

Just a FYI. If your session terminates/crashes instead of locking it might be caused by this

I had screen blacking enabled in nxserver settings and currently it seems to crash Xorg on session switch/lock.

Ataraxy commented on 2022-02-10 06:51 (UTC) (edited on 2022-02-10 07:01 (UTC) by Ataraxy)

% sudo pacman -Qk nomachine
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/nxclient.tar.gz (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/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

homerhsing commented on 2021-11-07 22:48 (UTC)

Hi! If the "nxserver" does not listen to port 4000, then edit file "/usr/NX/etc/server.cfg", set "StartNXDaemon" to "Automatic", set "EnableFirewallConfiguration" to "1", then restart "nxserver". The problem should be fixed then.

parkerlreed commented on 2021-09-30 06:21 (UTC)

Disregard. I had set the service to manual start (within the GUI settings) forever ago, uninstalled, and it remembered upon reinstalling.

parkerlreed commented on 2021-09-21 21:40 (UTC)

@galvez_65 Still nothing relating to 4000 :(

$ sudo netstat -tulpn | grep nx
tcp        0      0*               LISTEN      2636/nxnode.bin     
tcp        0      0*               LISTEN      2582/nxserver.bin   
tcp        0      0*               LISTEN      2636/nxnode.bin     
tcp        0      0*               LISTEN      2658/nxclient.bin   
tcp6       0      0 ::1:7001                :::*                    LISTEN      2636/nxnode.bin     
udp     8448      0*                           2582/nxserver.bin   
udp        0      0  *                           2582/nxserver.bin   
udp     1280      0 *                           2631/nxexec   

galvez_65 commented on 2021-09-21 21:11 (UTC)

@parkerlreed I ran sudo netstat -tulpn to list it. Interesting when I run sudo netstat -atu (which is supposed to list open ports) it's not listed

parkerlreed commented on 2021-09-21 20:43 (UTC)

@galvez_65 that's the thing. That's all my open ports related to nx. Nothing else shows up.

nxsever.service claims it's running fine and no errors/warnings.

galvez_65 commented on 2021-09-21 20:16 (UTC)

@parkerlreed look for nxd, on my machine that's how it's listed

parkerlreed commented on 2021-09-21 19:12 (UTC)

Did something change? nxserver seems to no longer be listening on 4000.

nxserver. 2003     nx   20u  IPv4  39800      0t0  TCP (LISTEN) 2056 parker   14u  IPv4  38680      0t0  TCP (LISTEN) 2056 parker   16u  IPv6  39865      0t0  TCP [::1]:7001 (LISTEN) 2056 parker   17u  IPv4  39866      0t0  TCP (LISTEN)
nxclient. 2078 parker    6u  IPv4  39876      0t0  TCP (LISTEN)

I can't find any notes about a new port. The main nxserver seems to randomize.

LinuxHG commented on 2021-07-21 20:03 (UTC) (edited on 2021-07-22 02:09 (UTC) by LinuxHG)

I searched and didn't see. Is anyone else getting the perl library error. I find it strange since the file is package with NX. /usr/NX/bin/nxserver.bin: error while loading shared libraries: cannot open shared object file: No such file or directory

EDIT:: Nevermind. Everything seems now to be working despite the missing dependencies.

galvez_65 commented on 2021-05-27 16:26 (UTC)

@blackhole, the popup can be turned off in the settings.

TechXero commented on 2021-05-27 16:15 (UTC)

In the software world 2 updates late = getting serious

blackhole commented on 2021-05-27 16:14 (UTC)

This is annoying because of nomachine popup at each boot asking to update...

galvez_65 commented on 2021-05-27 16:13 (UTC)

"Seriously" out of date is a bit harsh, 7.5.2 just came out last week and 7.6.2 just came out yesterday.

TechXero commented on 2021-05-27 15:00 (UTC)


Seriously out of date. 2 updates were released since.. Latest being 7.6.2. Kindly update...

Thanks ;)

blackhole commented on 2021-05-27 09:18 (UTC)

4.6.2_4 is out! Please update

gchamon commented on 2021-05-19 17:13 (UTC) (edited on 2021-05-19 18:39 (UTC) by gchamon)

updating nomachine to 7.5.2:

diff --git a/PKGBUILD b/PKGBUILD
index f17ff7d..9071874 100644
@@ -11,8 +11,8 @@ _autofirewall=n

@@ -30,13 +30,13 @@ options=('!strip')
 conflicts=('nxmanager' 'nxwebplayer' 'nxserver' 'nxnode' 'nxclient')
 depends=('bash' 'openssh' 'nawk')
 optdepends=('xorg-xauth: allows logging into a headless machine')

sha512 to md5 checksum is a downgrade, but that is what is provided in the download page

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:

Set to y to enable nomachine service autostart


Set to y to enable firewall autorules



runnytu commented on 2021-02-20 13:28 (UTC)

@cheezsteak, It's working ok, nxserver.service is always starting, and you see the icon on your desktop, but if you look in server status/ports you'll see the service in port 4000 are stopped and "Start the automatic service at startup" checkbox is disabled, even if you search devices in your LAN can see the PC but if you attempt to connect it will be rejected because is no NX service running.

I updated the package with update script when it's updated, and with disable autostart by default, I'll pin a warning and info for changing this behavior.

cheezsteak commented on 2021-02-17 18:54 (UTC) (edited on 2021-02-17 18:58 (UTC) by cheezsteak)

@galvez_65 sorry I was looking at the server.cfg.sample file not the server-fedora.cfg.sample file in nxserver.tar.gz. The config file is being edited correctly and is installed on my system with both StartNXDaemon Manual and EnableFirewallConfirguration 0 set.

However, the nxserver.service is still running and enabled after installing the package. I'm suspecting it's a problem with the upstream script nxserver not repsecting it's own configuration rules. If someone else can confirm this is true, I'd just give up on offering PKGBUILD options and just have the package scream "REMOTE DESKTOP ACCESS IS ENABLED FOR YOUR MACHINE" as loud as possible.

galvez_65 commented on 2021-02-17 17:24 (UTC)

@cheezsteak not sure I follow, I just checked the and the sample config file is present and contains the comments listed in the PKGBUILD that sed is looking for. I've not recently tested that changing the defaults works so I can't comment on that yet

cheezsteak commented on 2021-02-17 15:55 (UTC)

Th upstream package stopped providing a full config file with commentted out defaults to just one option and copyright. The sed commands in the PKGBUILD were looking for the comments to replace them but not making any changes. The PKGBUILD should now use the commands below instead of the sed commands.

echo "EnableFirewallConfiguration 0" >> NX/etc/server-fedora.cfg.sample
echo "StartNXDaemon Manual" >> NX/etc/server-fedora.cfg.sample

galvez_65 commented on 2021-02-17 15:42 (UTC)

The flags not working is definitely an issue that should be addressed. I wonder what changed in the config files ?

cheezsteak commented on 2021-02-17 15:32 (UTC)

@galvez_65 a sticky would be better than nothing but I just don't understand the merit defaulting to enabling the service over not. Saying "users should be reviewing the PKGBUILD" doesn't justify being insecure by default. If the maintainer were to switch they could still say "users should be reviewing the PKGBUILD" if any users complain about the service not being automatically.

Also the flags don't seem to work. I changed them to n as instructed, stopped and disabled nxserver.service , uninstalled nomachine, and reinstalled with makepkg -si. The warning message didn't print but nxserver was started after the install finished.

Looking into server.cfg.sample, there's only ServerRoot = "/usr/NX" and no commented out configurations. So these commands from the PKGBUILD make no changes to the package.

sed -i 's/#EnableFirewallConfiguration 1/EnableFirewallConfiguration 0/' NX/etc/server-fedora.cfg.sample
sed -i 's/#StartNXDaemon Automatic/StartNXDaemon Manual/' NX/etc/server-fedora.cfg.sample

galvez_65 commented on 2021-02-17 14:16 (UTC)

@cheezsteak While I won't argue that this package breaks with Arch norms, this is the AUR and users should be reviewing the PKGBUILD along with .install files to understand what they are doing. If this package were in the main repos, then yes what you describe would be the norm, but here I'm just thankful that someone put this together and is maintaining it. The same thing recently happened with tailscale, in the AUR it enabled the service automatically, once it was moved to the main redo that behavior was changed. Perhaps a sticky note should be added here to indicate that the default behavior is to enable by default and can be changed in the PKGBUILD file?

cheezsteak commented on 2021-02-16 21:18 (UTC)

I would like to relitigate the default behavoir of enabling nxserver and opening the ports by default. While I appreciate the maintiner providing configuration variables and warning notices, those settings ought be secure by default.

It's particularly egregious because this package provides both the server and the client software. So users installing the package on their home machine to remote into work could inadvertently expose remote desktop access to their home machine.

I understand the upstream package is insecure by default but that doesn't justify this package continuing that irresponsibility. I'm also not entirely sure that changing the default behavior will break anyone's existing setups. New installers must enable the service and open the ports, but that's standard behavior for arch packages and can be addressed with a pinned comment and/or different warning message. Users with this package already installed, who want the service enabled, will already have it enabled.

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.

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!

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.


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)


Thank you very much. I will try it.

lateparty commented on 2020-10-01 14:55 (UTC)

Looks like nomachine dont store old versions of their software (there is an official forum post of theirs that backs this up)

I manually edited the PKGINFO file to point to the latest version and release, and I did the sha512sum and it installed fine. Working fine too. Last version was broken.

chema commented on 2020-10-01 12:43 (UTC)

NoMachine is failing to check nomachine_6.11.2_1_x86_64.tar.gz checksum. I don't known if this is the correct site to inform about this.


Le_Birlante commented on 2020-10-01 10:57 (UTC)

@hcjl, @heavysink

yeah, I received the email too. Ye Lo and Behold !... this took upstream a "mere" three and a half months to solve. It seems that there are not many users out there using nomachine for ARMv7, since they haven't exactly rushed this fix.

But well, that's spilled milk under the bridge. What's important is that it seems we're back on track again and we'll be able to continue using nomachine.

hcjl commented on 2020-09-29 16:10 (UTC) (edited on 2020-09-29 16:11 (UTC) by hcjl)

@heavysink, @Le_Birlante, just received this from NoMachine. Seems like there is hope ;-)

TROUBLE REPORT: Updates to TR06R09747 on 2020-09-29 Cannot run NoMachine sessions on ARMv7 devices with kernel 5.4.42 or later Reason was: TR solved in version 6.12.3.

hcjl commented on 2020-09-21 08:37 (UTC)

@heavysink, @Le_Birlante, for me the problem still persists in 6.11.2 with the armv7h version. I also registered to get notifications about the mentioned bug, but never got notified ;-)

heavysink commented on 2020-09-20 15:30 (UTC)


I have already reported this issue at June and there is a ticket about it. Now the ticket is still open. Could you check if 6.11.2 still have the pow_infinite problem?

runnytu commented on 2020-09-16 18:41 (UTC)

@jichu4n, Done.

jichu4n commented on 2020-09-15 23:28 (UTC)

Hi runnytu!

Would it be possible to also add pentium4 as a supported architecture? This architecture is used by Arch Linux 32 for Pentium 4 and later 32-bit Intel CPUs, and so can just use the same NoMachine binaries as i686.

Here's a patch I tested on Arch Linux 32:

Thanks in advance!

tetamusha commented on 2020-08-30 10:58 (UTC)

I have a problem in which, under the bspwm window manager, all of the Unity and XFCE specific .desktop files are still shown. I don't know if this has something to do with my menu application (rofi) or if the configuration inside the .desktop is invalid.

kirk commented on 2020-07-01 15:02 (UTC)

Is it possible to install only nxserver and necessary daemons on my remote machine I want to access into? I don't need the client there since I'm gonna use from the client to access the remote machine.

galvez_65 commented on 2020-06-22 02:12 (UTC) (edited on 2020-06-22 02:12 (UTC) by galvez_65)

@LoopBack It's documented in the PKGBUILD file, you need to edit it to turn that off.

LoopBack commented on 2020-06-22 01:08 (UTC)

Recently with every update , the service is started and enabled at startup. I keep having to stop it and disable autostart with PC.

How do I stop this insecure behavior?

Thank you!

hcjl commented on 2020-06-20 13:21 (UTC)

@Le_Birlante, thanks for addressing this to NoMachine. I am also waiting for the fix.

RLLBcheese commented on 2020-06-17 11:26 (UTC)

$pkgver needs to be updated to 6.11.2. 6.10.12 is producing a webpage AFAICT.

You can work around the out-of-date package by downloading (or as appropriate for your $arch), running sha512sum on that file, updating the $pkgver and appropriate sha512sum_$arch line in the pkgbuild, then running makepkg -si.

greyltc commented on 2020-06-16 19:28 (UTC)

checksums failing for anyone else?

lucasrizzini commented on 2020-05-27 08:00 (UTC)

I don't know if this is a joke or not. Just go search through settings, man.

bradsk88 commented on 2020-05-26 21:37 (UTC)

Does anyone know how to configure this to use a different port than the default 4000?

galvez_65 commented on 2020-05-16 15:50 (UTC)

Anyone having issues connecting to a server running GDM? with GDM 3.36 if I try to remote into a machine which I am not already logged into I get a white screen. If I am physically logged in I can remote in without issue. Rolling GDM back to 3.34 resolved the issue for me.

pmatos commented on 2020-05-12 18:39 (UTC)

I am getting:

==> Validating source_x86_64 files with sha512sums... nomachine_6.9.2_1_x86_64.tar.gz ... FAILED

hcjl commented on 2020-05-11 10:17 (UTC)

@Le_Birlante, I have exactly the same problem (RPI4, Archlinux ARM, XFCE). So unfortunately just a confirmation, not a solution :-(

Le_Birlante commented on 2020-05-04 21:22 (UTC) (edited on 2020-05-04 21:32 (UTC) by Le_Birlante)

Hi there,

I think this is upstream territory, but anyway, here it goes in case someone here could confirm this one.

Scenario : Raspberry PI 4 running Arch Linux for ARM, KDE+Plasma, NoMachine 6.9.2 package. Eeverything runs flawlessly for weeks, not even a single problem.

The problem: latest arch/arm kernel updates (over the past week there have been two linux-raspberrypi4 updates, latest is 4.5.35-1) seem to have broken NoMachine. It will simply refuse to start.

If you go to nxserver.log, you can see NX is trying to get an instance up and running, but to no avail:

2020-05-04 22:58:09 254.556 21823 NXSERVER WARNING! Process '/usr/NX/bin/nxexec --node --user xxx --priority realtime --mode 0 --pid 16' with pid '23454/23454' finished with exit code 127 after 1,453 seconds. 2020-05-04 22:58:09 255.262 21823 NXSERVER WARNING! FBA3ED947BAD40D54C4D64B030FDC4BA nxnode died with exit code 127.

2020-05-04 22:58:09 372.189 21823 NXSERVER WARNING! Session FBA3ED947BAD40D54C4D64B030FDC4BA crashed on display 0.

2020-05-04 22:58:10 916.236 21823 NXSERVER WARNING! Process '/usr/NX/bin/nxexec --node --user xxx --priority realtime --mode 0 --pid 14' with pid '23601/23601' finished with exit code 127 after 1,528 seconds.

2020-05-04 22:58:10 916.821 21823 NXSERVER WARNING! AE162AD84888CEDA4DC8F1DB456033EB nxnode died with exit code 127.

2020-05-04 22:58:11 007.321 21823 NXSERVER WARNING! Session AE162AD84888CEDA4DC8F1DB456033EB crashed on display 0.

I inspected one of those crashed sessions ( /usr/NX/var/log/node/F-C-session_hex_code_here/session ) and this is the only suspect I could see :

Session: Starting session at Mon May 4 22:58:16 2020. Info: Agent running with pid 24113. Info: Slave server running with pid 24186. Info: Display running with pid 24187. Info: Listening to slave connections on port 12003. Info: Audio client started with pid 24195. Info: Audio server started with pid 24194. Info: Display server started with pid 24196.

=======>>>>>> /usr/NX/bin/nxnode.bin: symbol lookup error: /usr/NX/lib/ undefined symbol: __pow_finite <<<<<<=====

Thing is, I am not sure whether the 'pow_finite' symbol failure was already present as a simple warning before the rpi4 kernel update, or whether it's indeed the culprit of NX crashing. Turns out, I had never before had to look at these logs, since everything was working ok, so perhaps the pow_finite thingie was always there and it has nothing to do with the current problem. Go figure...

Long story short: Nomachine for RPI4 is broken since two kernel updates ago (more or less a week ago, talking in days). If you use NX with your PI4 like me, try not to upgrade the kernel.

regards !

runnytu commented on 2020-04-29 18:26 (UTC)

@smekkleysa, both are in the base package, that is the minimum you should have installed, and never are in the depends part of an aur package.

smekkleysa commented on 2020-04-27 10:13 (UTC)

For super minimal setup, tar and hostname command are needed.

jichu4n commented on 2020-02-21 03:59 (UTC)

@runnytu Awesome, thank you!!

runnytu commented on 2020-02-20 20:22 (UTC)

@jichu4n, done with the same version to avoid other users to upgrade.

jichu4n commented on 2020-02-17 00:11 (UTC)

First, thanks a lot for making & maintaining this package! I use it all the time on x86_64 and it works great.

However, would it be possible to add aarch64 as a supported architecture? I'm not sure what the difference between the two are, but Manjaro ARM uses aarch64 instead of armv8h, and trying to install this package as-is fails. However, just adding a few lines into the PKGBUILD to make aarch64 behave the same as armv8h seems to work fine for me.

Here's a patch I tested on Manjaro ARM on the Pinebook Pro:


electricprism commented on 2020-01-13 07:07 (UTC) (edited on 2020-01-13 07:07 (UTC) by electricprism)

For some reason it installs and fails when starting "nxserver" systemctl service.

And for some reason this seems to fix that? I'm not sure if this is a solution or not in those cases. sudo mv /etc/NX/nxserver /etc/NX/nxserver.bak && sudo ln -s /usr/NX/bin/nxserver /etc/NX/nxserver

galvez_65 commented on 2020-01-05 20:59 (UTC)

to use with gnome and wayland I had to follow these instructions:

Gabriel_Gomes commented on 2020-01-02 23:29 (UTC)

Excelent package

runnytu commented on 2019-12-19 19:18 (UTC)

@blackhole, Server preferences/Updates, uncheck Automatically check for updates checkbox and apply.

blackhole commented on 2019-12-19 17:45 (UTC)

Is possible to get rid of nomachine update message?

runnytu commented on 2019-12-11 18:56 (UTC)

@liberodark, it's already supported as armv8h.

liberodark commented on 2019-12-04 23:39 (UTC) (edited on 2019-12-04 23:41 (UTC) by liberodark)

Please use that for support RPI4

Le_Birlante commented on 2019-10-23 12:21 (UTC)

edit: a word of caution

The patch works perfectly, but only when a kde/plasma session has been started.

i.e., sddm , for example, isn't available for NM. Not until you manually log on and spawn a Kde/plasma session.


Le_Birlante commented on 2019-10-22 19:32 (UTC)

Damn... it worked like a charm.

runnytu: thank you a lot.


runnytu commented on 2019-10-22 18:49 (UTC)

@jnko, @Le_Birlante & all plasma users, Added the fix for Plasma 5.17 on X86_64 with the same version to avoid non X86_64/plasma users to reinstall, and don't use "development" packages.

jnko commented on 2019-10-22 10:10 (UTC)

Here's the link for the patched package fixing the KDE 5.17 issue. I can validate that it's working fine.

Le_Birlante commented on 2019-10-22 09:21 (UTC) (edited on 2019-10-22 09:22 (UTC) by Le_Birlante)

Update: nomachine devs have opened a thread here <> where they're discussing the kde5.17+NM problem.

They have come up with a patch which seems to fix the problem, and they're offering it via email to the users who are on that thread.

runnytu, do you think you could grab that patch and integrate it in your NoMachine arch package ? That would save the day for a few of us xD


runnytu commented on 2019-10-21 18:57 (UTC)

@jnko & @galvez_65, added nawk as a dependency.

galvez_65 commented on 2019-10-18 19:06 (UTC)

I second adding nawk as a dependency

Le_Birlante commented on 2019-10-18 18:44 (UTC)

With last plasma update nomachine tray icon missing. Any idea?

It's far worse than that. Latest plasma update (5.17) has changed the usual KDE plasma startup procedure, from /usr/bin/startkde to /usr/bin/startplasma-x11.

This has broken nomachine (at least, if you were using it with KDE plasma, which is my case) since NM will try to start a session by calling /usr/bin/startkde, which in turn will fail, leaving you without being able to connect to your remote host via nomachine.

I've tried modifying nomachine's node.cfg (namely, DefaultDesktopCommand and CommandStartKDE directives) to point to /usr/bin/startplasma-x11 instead of /usr/bin/startkde, but to no avail.

It should be noted, though, that startkde was a shell script, while startplasma-x11 is a full-fledged ELF binary, so I take it for granted that such a simple fix as changing "startkde" for "startplasma-x11" in node.cfg wasn't going to work...

As for now, I do not know what else to do. KDE-plasma + NoMachine seems to be plain broken, and I think this should be fixed upstream, but right now I've run out of ideas.

Advice: do not upgrade to plasma 5.17 if you are using nomachine and you depend on it for accessing your servers !


jnko commented on 2019-10-18 16:27 (UTC)

Please add "extra/nawk" as dependency, otherwise every call of nxserver or tools will produce "/usr/NX/bin/nxserver --version awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator "

blackhole commented on 2019-10-17 09:54 (UTC)

With last plasma update nomachine tray icon missing. Any idea?

Arsen6331 commented on 2019-10-06 01:38 (UTC) (edited on 2019-10-06 01:38 (UTC) by Arsen6331)

Open the PKGBUILD and change the checksum to "SKIP" to bypass checksum

faky commented on 2019-09-17 19:16 (UTC)

Any solutions to checksum fail?

Ataraxy commented on 2019-05-25 05:47 (UTC) (edited on 2019-05-25 05:48 (UTC) by Ataraxy)

The link <> redirects to <> causing sha512sum check to fail.

runnytu commented on 2019-02-10 12:02 (UTC)

@greyltc, optdepends added with the same version to avoid users to reinstall, the other question is the default config on nomachine, and I don't want to change that, for that reason, I created these options to anyone can disable if he/she wants, but keeping the original behavior of the package for default.

greyltc commented on 2019-02-07 21:32 (UTC) (edited on 2019-02-07 21:38 (UTC) by greyltc)

Can we please have _autofirewall=y and _autoservice=y both set to n by default? Having the PKGBUILD do these things by default is very unexpected and potentially dangerous.

Also please add xorg-xauth to optdepends that allows one to log into a headless machine (with a supported window manager).

electricprism commented on 2019-01-08 07:27 (UTC)

This is generally considered bad practice but it will make nxserver.service run

ln -s /usr/NX/lib/ /usr/lib/ ln -s /usr/NX/lib/ /usr/lib/

marcin commented on 2018-08-03 01:03 (UTC)

FYI: This comes with nxplayer (/usr/NX/bin/nxplayer) which can be used to connect to nxservers. For some reason arch wiki on nx does not mention this and only says about nxclient.

brittyazel commented on 2018-06-18 15:52 (UTC) (edited on 2018-08-01 08:40 (UTC) by brittyazel)

The latest NoMachine isn't compatible with the version of ffmpeg in the main repos. As a result, h264 isn't working at all. I tested a couple of the ffmpeg-compat packages with no success. Any ideas?

update* Cool, installing the compat package and symlinking '/usr/lib/ > /usr/NX/lib/' and '/usr/lib/ > /usr/NX/lib/' worked like a charm.

runnytu commented on 2018-06-13 20:41 (UTC)

@mrfabjr, try again, it was outdated.

mrfabjr commented on 2018-06-13 13:43 (UTC) (edited on 2018-06-13 13:49 (UTC) by mrfabjr)

Getting the following errors:

curl: (22) The requested URL returned error: 404 Not Found

==> ERROR: Failure while downloading Aborting... ==> ERROR: Makepkg was unable to build nomachine.

Tried installing using:


$ yaourt -S nomachine

I've done the following:

Updated system

Refreshed Databases

no luck.


runnytu commented on 2018-06-02 13:36 (UTC)

@meriops, fixed.

meriops commented on 2018-06-01 19:11 (UTC)

makepkg complains that the "conflict" entry contains illegal characters. This entry should be: conflicts=('nxmanager' 'nxwebplayer' 'nxserver' 'nxnode' 'nxclient') rather than the current:<br> conflicts=('nxmanager nxwebplayer nxserver nxnode nxclient')

kubrick commented on 2018-04-28 10:48 (UTC)

Hi, is there a way to fix this problem permanently please?

parkerlreed commented on 2018-02-15 17:22 (UTC)

Ahh cheers, missed that.

runnytu commented on 2018-02-14 20:41 (UTC)

@parkerlreed, there is an option in the PKGBUILD to disable nomachine service autostart, you only need to change it to no, also there is a banner during installation informing you "No Changes To Automatic Service Start And Firewall Automatic Rules" if you don't touch the variable.

@brittyazel, fixed.

parkerlreed commented on 2018-02-14 16:45 (UTC)

The post install command enables the service automatically...

Might want to make a note of this in the post install script in case the user installing it only wants to use it as a client.

brittyazel commented on 2018-02-13 21:24 (UTC)

For anyone having issues with NoMachine not using h.264, it's an issue with the included in /usr/NX/lib. Just rename this to or something, and restart NoMachine and h.264 should work (granted you need to have everything else set up correctly too). This error is common when a software program comes bundled with a verseion of libstdc++ that is out of date compared to the one in Archlinux. (looking at you MATLAB and Steam)

@runnytu, perhaps it might be usefull to add a command to the build script that renames this file so that people won't run into this issue.

robit.a commented on 2018-02-10 22:01 (UTC)

thanks huitseeker

huitseeker commented on 2018-02-10 21:28 (UTC)

Please consider this diff for an update:

burningbronx commented on 2018-01-23 15:51 (UTC)

Somehow after the installation I ended up with bad licenses and service wouldn't start, had to get the *.lic files from a proper 6.0.66 installation.

blackhole commented on 2018-01-11 08:04 (UTC) (edited on 2018-01-11 08:04 (UTC) by blackhole)

Anyone know how to fix the typing slowness when connected to another linux machine? Really it is not the typing that is slow, but the refresh of little areas of the screen. Sometime I see the typed letter only if I drag the window a little. Very strange...

fatalis commented on 2018-01-08 00:59 (UTC)

Here's a patch to enable x264 for a much better experience over the default VP8:

electricprism commented on 2017-12-01 02:12 (UTC) Needs to be Checksum needs to be updated also.

shyokou commented on 2017-11-20 02:29 (UTC)

@steadybright: Thank you! NoMachine 6 seemed to act slightly different from its previous 5 when I tried to connect locally ...

steadybright commented on 2017-11-15 03:17 (UTC)

@shyokou: I installed 6.0.62_6, and it works fine.

steadybright commented on 2017-11-15 03:16 (UTC)

I updated the PKGBUILD locally and installed version 6.0.62_6 from Nomachine. Deleting my previous post.

shyokou commented on 2017-11-15 02:27 (UTC)

Anybody tried the new 6 released as NoMachine for Linux 6.0.62_6 et cetera ???

Ataraxy commented on 2017-09-07 04:06 (UTC)

I get multiple warnings like: warning: could not get file information for usr/NX/etc/NX/ Are these important, or could they be suppressed?

runnytu commented on 2017-08-12 12:27 (UTC)

Hello, Bump to new version 5.3.10-1.

runnytu commented on 2017-06-14 20:44 (UTC)

Hello, Bump to new version 5.3.9-2 fixing nxusb share.

runnytu commented on 2017-06-07 20:13 (UTC)

Hello, Bump to new version 5.3.9-1.

ToastedBits commented on 2017-06-01 04:39 (UTC)

Anyone else having issues getting USB sharing to work? Googling around doesn't reveal much, but it appears there is supposed to be some kind of nxusb daemon running and an associated kernel module supported by nomachine. Running the script found in /usr/NX/scripts/restricted/ doesn't appear to do anything either.

runnytu commented on 2017-05-04 19:19 (UTC)

Hello, Bump to new version 5.2.21-1.

adial commented on 2017-05-03 19:22 (UTC)

FYI: running a shaw512sum against the downloaded 5.2.21_1 package and updating the version and hash on the package installer intstalls the new version fine. Just mentioning as an option until runnytu gets back from what I'm sure is a much needed vacation! Thanks for all your work.

kristianjgs commented on 2017-04-30 00:55 (UTC)


webdawg commented on 2017-04-25 19:06 (UTC)

Gotta do what you gotta do man, have a great holiday!

runnytu commented on 2017-04-18 11:58 (UTC)

I'm on holidays without a computer until 4 of may, cannot update after this day, apologies

dlford commented on 2017-02-08 05:09 (UTC) (edited on 2017-02-09 01:11 (UTC) by dlford)

UPDATE: got it working - After reverting from a backup to a working system, I did the nomachine update from aur first, then did -Syu updates, and all is well. It's possible that one of those packages has updated again since yesterday or something tripped up in the plasma ecosystem because there were so many updates piled up, either way it's working now. --------------------------------------------------------------------------- Anybody else have their nxserver break today? I'm running KDE Plasma, did an Syu update and it broke nxserver, tried updating nomachine from 5.2.11 to 5.2.11-1, reinstalled xorg, plasma, sddm, no luck. The error was something to the effect of "cannot access . in . does not exist" I'll have to reinstall it again tomorrow to get the exact error message. One of the following updates is the culprit: [2017-02-07 15:45] [ALPM] upgraded bluedevil (1:5.9.0-1 -> 1:5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kdecoration (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded breeze (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded breeze-gtk (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded drkonqi (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kactivitymanagerd (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded libepoxy (1.3.1-1 -> 1.4.0-1) [2017-02-07 15:45] [ALPM] upgraded kde-cli-tools (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kde-gtk-config (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded libksysguard (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded milou (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kscreenlocker (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kwin (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded plasma-integration (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kuiserver (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded plasma-workspace (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kdeplasma-addons (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kgamma5 (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded khotkeys (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kinfocenter (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kmenuedit (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded libkscreen (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kscreen (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded ksshaskpass (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded ksysguard (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kwallet-pam (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kwayland-integration (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded kwrited (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded oxygen (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded polkit-kde-agent (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded systemsettings (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded plasma-desktop (5.9.0-1 -> 5.9.1-2) [2017-02-07 15:45] [ALPM] upgraded plasma-nm (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded plasma-pa (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded plasma-sdk (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded plasma-workspace-wallpapers (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded powerdevil (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded sddm-kcm (5.9.0-1 -> 5.9.1-1) [2017-02-07 15:45] [ALPM] upgraded user-manager (5.9.0-1 -> 5.9.1-1)

Saren commented on 2017-02-04 06:52 (UTC)

The source really hates multithreaded download, the server blocks my IP for 15 minutes if I use aria2 to download it.

runnytu commented on 2017-02-02 19:31 (UTC)

Hello, Bump to new version 5.2.11-1.

runnytu commented on 2017-01-06 14:45 (UTC)

@blackhole, and with this: "/usr/bin/lxqt-session -e LXQT"

blackhole commented on 2017-01-05 22:21 (UTC)

Unfortunately /usr/bin/lxqt-session will give only a black screen, with only the windows of two applications that I have set to autostart. No bottom bar in this case. The only (not user friendly...) method is to open a ssh session and issue the command "systemctl start sddm"

runnytu commented on 2017-01-05 20:56 (UTC)

@blackhole, startlxqt isn't the correct command, it should /usr/bin/lxqt-session with perhaps some option more.

blackhole commented on 2017-01-05 11:33 (UTC)

I have this problem: Maybe this version cannot launch my already installed remote Desktop if system is in

czk commented on 2016-11-29 01:03 (UTC)

@runnytu Much appreciated. I will give that a whirl on the next nomachine upgrade.

runnytu commented on 2016-11-28 23:03 (UTC)

@czk, I fixed the Fedora variable error, equally nomachine was working ok even with the error, furthermore i added two options, first one to disable the service autostart and the second to disable the automatic firewall rules, only is necesary to edit the PKGBUILD file, and change the _autoservice and _autofirewall variables in the begin of the PKGBUILD and continue with the build process, i don't change the package version to avoid users that don't want to change the autostart options, they don't have need to reinstall the package.

czk commented on 2016-11-26 11:05 (UTC) (edited on 2016-11-26 11:05 (UTC) by czk)

machine.install runs `/usr/NX/nxserver --install fedora`. This results in an error I noticed during upgrade from 5.1.54-1 to 5.1.62-1: ``` /usr/NX/scripts/setup/nxclient: line 4243: [: -ge: integer expression expected ``` That's because `majorFedoraVersion` var won't get set on non-Fedora systems. I haven't verified whether this leads to any problems. Not using NX much recently. @runnytu, can you please check this out? I have also rembered 2 other security issues besides the firewall problem I described on 2016-10-24: this software will enable and start the nxserver.service on your machine. Auto-starting and auto-enabling a service, let alone a network service, and punching holes in host's firewall is a practice hard to accept. Please do someting about this before the next package release. It is a great piece of software and kudos for maintaing it, yet this issues are too serious to be ignored. Auto-starting the client app after the installation doesn't look OK either.

runnytu commented on 2016-11-23 20:46 (UTC)

Hello, Bump to new version 5.1.62-1, added ssh dependency.

czk commented on 2016-10-24 08:57 (UTC)

NX is no doubt a great piece of software. But it has the following issues the users should be aware of: - nxserver.service opens TCP 4000 port to incoming connections without asking, even if you have your firewall set-up to block all incoming connections. And it will close the port back on NX service termination, again without letting the user control this. If you want to be able to manage the firewall yourself, edit lines 84 and 87 in /usr/NX/scripts/restricted/ to your liking. I simply commented them out. - It forces sshd.service start on your machine, due to "Wants=sshd.service" in /usr/lib/systemd/system/nxserver.service. I guess this also means that the nomachine package should require opnssh package explicitely.

runnytu commented on 2016-10-01 14:46 (UTC)

Hello, Bump to new version 5.1.54-1, added armv8h arch too.

runnytu commented on 2016-08-04 18:35 (UTC)

Hello, Bump to new version 5.1.44-1.

runnytu commented on 2016-07-27 18:20 (UTC)

Hello, Bump to new version 5.1.42-1.

runnytu commented on 2016-07-20 18:40 (UTC)

Hello, Bump to new version 5.1.40-1.

electricprism commented on 2016-07-20 06:24 (UTC)

Set Version to 5.1.40 and set sha256 hash code to: 'SKIP' Now if only I could figure out how to suggest a commit to the GIT PKGBUILD

electricprism commented on 2016-07-19 23:32 (UTC)

==> Validating source_x86_64 files with sha512sums... nomachine_5.1.26_1_x86_64.tar.gz ... FAILED

ryester19 commented on 2016-05-31 01:21 (UTC) (edited on 2016-05-31 01:24 (UTC) by ryester19)

Should xorg-xauth be added as a dependency? I was getting "NXSERVER ERROR! checkLocalSession: xauth not found in standard paths. Contact system administrator." errors inside the nxserver.log file, and not able to connect to the current X11 session, until I installed that package

runnytu commented on 2016-05-06 21:08 (UTC)

Hello, Bump to new version 5.1.26-1.

runnytu commented on 2016-04-26 20:31 (UTC)

Hello, Bump to new version 5.1.24-1 & armv6h and armv7h support.

necopinus commented on 2016-04-24 16:24 (UTC)

Quick request: armv6h and armv7h sources (since NoMachine provides these now). Thanks!

runnytu commented on 2016-04-22 22:08 (UTC)

Hello, Bump to new version 5.1.22-1.

runnytu commented on 2016-03-03 19:49 (UTC)

Hello, Bump to new version 5.1.9-1.

electricprism commented on 2016-02-27 07:11 (UTC)

@runnytu, thanks for this, before 5.xx I couldn't get any other VNC or XRDP to work, certainly helped relieve headaches.

runnytu commented on 2016-02-26 19:11 (UTC)

Hello, Bump to new version 5.1.7-1.

runnytu commented on 2016-01-31 11:52 (UTC)

Hello, Bump to new version 5.0.63_1.

serialoverflow commented on 2016-01-16 15:36 (UTC) (edited on 2016-01-23 08:09 (UTC) by serialoverflow)

For current version use With 5.0.58 integrity check fails and installation is broken: ==> Validating source files with sha512sums... nomachine_5.0.58_1_x86_64.tar.gz ... FAILED Running NX post_install script... /tmp/alpm_vCMZdv/.INSTALL: line 4: /usr/NX/nxserver: No such file or directory error: command failed to execute correctly

runnytu commented on 2016-01-05 21:01 (UTC)

Hello, Bump to new version 5.0.58_1.

runnytu commented on 2015-11-28 13:46 (UTC)

Hello, Bump to new version 5.0.53_1.

Manouchehri commented on 2015-10-23 23:40 (UTC)

Changes also sent via email.

runnytu commented on 2015-10-21 20:27 (UTC)

Hello, Bump to new version 5.0.47_1.

jascha commented on 2015-10-21 07:05 (UTC)

5.0.47 has been released :)

runnytu commented on 2015-10-02 19:23 (UTC)

Hello, Bump to new version 5.0.43_1.

vollekannehoschi commented on 2015-10-02 09:55 (UTC)

5.0.43_1 is out and the current 4.6.16 files are no longer available it seems. I get HTTP 404s for them :(

runnytu commented on 2015-09-28 19:16 (UTC)

Hello, Bump to new version 4.6.16-1.

Sandman007 commented on 2015-09-09 21:03 (UTC)

@runnytu. Thank you! I actually just relized that before I was using pkgrel=16 before and so it wasn't compiling. Now its compiled and I have it installed. Thank you so much!

Sandman007 commented on 2015-09-09 20:37 (UTC)

@runnytu Thanks. I had actually tried this exact thing but if it works for u I must have made a typo somewhere. I'll give it another go. Thanks again kind sir

runnytu commented on 2015-09-09 20:34 (UTC)

@Sandman007, Changing this builds and installs ok: pkgver=4.6.16 pkgrel=1 for x86_64: pkgrel=1 sha256sums=('4c1abc76d844f04f24e5fadf06bb720275dacd3e71aacceb6380bc8755a0f996') for i686: pkgrel=1 sha256sums=('c55dcdc895f4427bc5d988467d8313ee2c0678caca6b3913ed53d5b247c3142f')

Sandman007 commented on 2015-09-09 15:14 (UTC)

This is insane. This package isn't usable anymore. It isn't installing. If you dont have time to maintain this package then let someone else pick it up. This is a critical package for some people. Now I have tried editing the pkgbuild myself with the updated URL and Checksum but it just won't compile. It fails on Line 3 when looking for nxserver. If someone can shed some light on how to get this working that would be great. Thanks!

dront78 commented on 2015-09-03 18:10 (UTC)


sibnull commented on 2015-08-06 05:17 (UTC)

Lastest version at this posting is 4.6.12_7

FreeK commented on 2015-06-15 17:05 (UTC)

should work on i686 and x86_64 now. Got some issues with aur4.

runnytu commented on 2015-06-11 19:53 (UTC)

Could you add i686 support how until now?

runnytu commented on 2015-06-07 10:25 (UTC)

Yes, it installs ok, but yaourt says always an update is available because in the AUR platform is uploaded nomachine 4.6.3-11 and i've got installed nomachine 4.6.3-7, this is the issue with this package, do you can arrange this?

FreeK commented on 2015-06-06 14:21 (UTC)

The archive for i686 is nomachine_4.6.3_7_i686.tar.gz, so i686's pkgrel is 7; 64bit archive is nomachine_4.6.3_11_x86_64.tar.gz, so x86_64's pkgrel is 11. I just installed the i686 package without any problems.

runnytu commented on 2015-06-06 12:16 (UTC)

Hi, the PKGBUILD is not ok, in i686 the pkgrel=7 and in aur is pkgrel=11, aur says always have an update (installed -7 aur -11) do you can arrange this?

FreeK commented on 2015-04-04 14:16 (UTC)

updated to 4.5.0_1

smekkleysa commented on 2015-04-04 02:13 (UTC)

4.5.0 is released.

pschmitt commented on 2015-02-21 22:55 (UTC)


FreeK commented on 2015-02-21 17:05 (UTC)

updated to 4.4.12_11 (x86_64) and 4.4.12_12 (i686)

pschmitt commented on 2015-02-21 16:24 (UTC)

The sha256sum for x86_64 should be updated. (5fbe413ece8e8371b94fc5f0cfba31f9eca828b74809d45662bf70ea6a6d207c)

FreeK commented on 2015-01-22 02:04 (UTC)

thanks, updated to the latest release.

fifthecho commented on 2015-01-20 16:18 (UTC)

4.4.6 is out. with md5sum 80f6c4dacc976ff4bfac30bf6655f6ad

pschmitt commented on 2014-12-18 15:40 (UTC)

4.4 is out. Here's an updated PKGBUILD:

FreeK commented on 2014-11-02 17:09 (UTC)

updated to the latest release.

Techman35 commented on 2014-11-02 16:50 (UTC)

Theres a new release 4.3.30 please update the PKGBUILD

fede2 commented on 2014-10-09 00:51 (UTC)

There's a new release, 4.3.23. Just tested it on my system after modifying the pkgver, pkgrel and sha signatures for the packages. Little note: pkgrel for x86_64 and i686 are different. 7 for 64 and 8 for 32bits. Thanks for the AUR package.

FreeK commented on 2014-08-19 12:58 (UTC)

Thanks for the info, just updated the PKGBUILD file.

erisrjr commented on 2014-08-12 02:57 (UTC)

Sorry for md5sum. sha256sum x86_64: d814805c0dcadda258772642816cc46be2f7e653da8b8f6011bc65cc901d7224 sha256sum i686: 85357c4da42e1bd3b45179bbe75748852084478dcdcddb5fe1a473658b78de77

erisrjr commented on 2014-08-12 02:48 (UTC)

This package has been updated to version 4.2.27_1 by nomachine. MD5SUN X86_64: 5369dd6a2ff6f954b4e227b52e001c1e MD5SUN i686: d888ba2eae0396676ed89e2e23e417f2 *Thank you for creating it.