Package Details: nomachine 8.14.2-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: 92
Popularity: 0.40
First Submitted: 2014-07-24 15:45 (UTC)
Last Updated: 2024-10-04 19:35 (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 2 3 4 5 6 7 8 9 .. 25 Next › Last »

torleif123 commented on 2023-02-13 18:35 (UTC)

I don't know if this is the right place to ask. But I just got a new m1 Mac running Asahi Linux aarch64. Is there anyway to get Nomachine for this architecture?

jal666 commented on 2023-02-08 16:37 (UTC) 

Set to y to enable nomachine service autostart
_autoservice=n

The above would be particularly helpful to have as the default. Otherwise, after a reboot you need to enter manually

sudo /usr/NX/bin/nxserver –restart

Which is annoying.

If you are reading this after the install,

sudo /etc/NX/nxserver --startmode nxd automatic

is a fix (thanks Britgirl!)

blackhole commented on 2023-01-07 10:52 (UTC)

Recently nothing is working... I have been using it for long time.

I have already tried a clean install.

Even if I enable nxserver systemd service or install with _autoservice=n I must enable it manually each time with

sudo /etc/NX/nxserver --restart

Moreover I cannot connect to lxqt server

Initially it seems to connect but after the process die

I can connect however from my Android smartphone

nikita240 commented on 2022-11-16 23:25 (UTC)

@runnytu thank you. Uninstalling and reinstalling fixed nxusb!

galvez_65 commented on 2022-11-16 21:59 (UTC)

@runnytu thanks for the explanation

runnytu commented on 2022-11-16 20:44 (UTC)

When you reinstall the same version nxusb isn't recompiled again, if you deinstall nomachine, and launch ls -l /usr/NX/bin/drivers/, you see nothing, if install again the nomachine package, and relaunch ls -l /usr/NX/bin/drivers/ you see the module compiled: -rw-r--r-- 1 root root 847336 nov 16 21:37 nxusb.ko

galvez_65 commented on 2022-11-16 19:48 (UTC) (edited on 2022-11-16 20:37 (UTC) by galvez_65)

@runnytu - thank you for the explanation. According to the nxupdate.log USB can not be compiled although linux-headers are installed. Not sure if it matters but the package was build on a different computer and installed via an internal repository.

nxusb compiles manually

runnytu commented on 2022-11-16 19:13 (UTC)

The dependencies are needed to build the package, the use of the rpm command (rpm-tools) and pkcheck (polkit), and the DKMS are for linking the correct linux-headers for your kernel in order to build the nxusb successfully.

nikita240 commented on 2022-11-16 07:52 (UTC)

Regression in 8.2.3. Nxusb no longer works.

gameslayer commented on 2022-11-14 06:21 (UTC) (edited on 2022-11-14 06:24 (UTC) by gameslayer)

Missing dependencies that need to be added to the PKGBUILD file

Building nomachine...
==> Making package: nomachine 8.2.3-1 (Mon 14 Nov 2022 16:20:08)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> rpm-tools
  -> dkms
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 25 Next › Last »