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

Damn... it worked like a charm.

runnytu: thank you a lot.

regards,

@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.

Here's the link for the patched package fixing the KDE 5.17 issue. I can validate that it's working fine. https://download.nomachine.com/44bef5297fe9efb3430b9fd47ad18b01/downloads/temporary/forum/nomachine_6.8.1_32_x86_64.tar.gz

https://download.nomachine.com/44bef5297fe9efb3430b9fd47ad18b01/downloads/temporary/forum/nomachine_6.8.1_32_x86_64.rpm

Update: nomachine devs have opened a thread here <https://forums.nomachine.com/topic/nx-wont-work-with-recent-kde-5-17> 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

regards,

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

I second adding nawk as a dependency

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 !

regards,

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 "

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

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