The source really hates multithreaded download, the server blocks my IP for 15 minutes if I use aria2 to download it.
Search Criteria
Package Details: nomachine 8.14.2-1
Package Actions
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: | 93 |
Popularity: | 1.38 |
First Submitted: | 2014-07-24 15:45 (UTC) |
Last Updated: | 2024-10-04 19:35 (UTC) |
Dependencies (7)
- bash (bash-devel-static-gitAUR, bash-devel-gitAUR, busybox-coreutilsAUR, bash-gitAUR)
- dkms (dkms-gitAUR, dkms-fast-zstdAUR)
- nawk (nawk-gitAUR)
- openssh (openssh-gitAUR, openssh-dotconfigAUR, openssh-dotconfig-binAUR, openssh-selinuxAUR, openssh-hpn-shimAUR, openssh-gssapiAUR)
- polkit (polkit-gitAUR, polkit-consolekitAUR)
- rpm-tools (rpm-tools-gitAUR)
- xorg-xauth (optional) – allows logging into a headless machine
Required by (0)
Sources (5)
- http://download.nomachine.com/download/8.13/Linux/nomachine_8.14.2_1_aarch64.tar.gz
- http://download.nomachine.com/download/8.13/Linux/nomachine_8.14.2_1_armv6hl.tar.gz
- http://download.nomachine.com/download/8.13/Linux/nomachine_8.14.2_1_armv7hl.tar.gz
- http://download.nomachine.com/download/8.13/Linux/nomachine_8.14.2_1_i686.tar.gz
- http://download.nomachine.com/download/8.13/Linux/nomachine_8.14.2_1_x86_64.tar.gz
Latest Comments
« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 25 Next › Last »
Saren commented on 2017-02-04 06:52 (UTC)
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.
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.
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