@Le_Birlante
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?
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.40 |
First Submitted: | 2014-07-24 15:45 (UTC) |
Last Updated: | 2024-10-04 19:35 (UTC) |
« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 25 Next › Last »
@Le_Birlante
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?
@jichu4n, Done.
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: https://gist.github.com/jichu4n/75bd2ad2a485cf1f4785908a1772a3b6
Thanks in advance!
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.
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.
@LoopBack It's documented in the PKGBUILD file, you need to edit it to turn that off.
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!
@Le_Birlante, thanks for addressing this to NoMachine. I am also waiting for the fix.
$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 http://download.nomachine.com/download/6.11/Linux/nomachine_6.11.2_1_x86_64.tar.gz (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.
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