Package Details: nomachine 8.11.3-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: 91
Popularity: 0.78
First Submitted: 2014-07-24 15:45 (UTC)
Last Updated: 2024-02-05 20:30 (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 .. 13 14 15 16 17 18 19 20 21 22 23 24 Next › Last »

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: https://www.nomachine.com/forums/topic/starting-lxqt-virtual-desktop Maybe this version cannot launch my already installed remote Desktop if system is in multi-user.target?

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

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