Same segfault here
Search Criteria
Package Details: nomachine 8.16.1-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: | 95 |
Popularity: | 0.40 |
First Submitted: | 2014-07-24 15:45 (UTC) |
Last Updated: | 2025-02-01 20:34 (UTC) |
Dependencies (7)
- bash (bash-devel-static-gitAUR, bash-devel-gitAUR, bash-gitAUR)
- dkms (dkms-gitAUR)
- nawk (nawk-gitAUR)
- openssh (openssh-gitAUR, openssh-dnatAUR, openssh-gssapiAUR, openssh-hpn-shimAUR, openssh-selinuxAUR)
- 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.16/Linux/nomachine_8.16.1_1_aarch64.tar.gz
- http://download.nomachine.com/download/8.16/Linux/nomachine_8.16.1_1_armv6hl.tar.gz
- http://download.nomachine.com/download/8.16/Linux/nomachine_8.16.1_1_armv7hl.tar.gz
- http://download.nomachine.com/download/8.16/Linux/nomachine_8.16.1_1_i686.tar.gz
- http://download.nomachine.com/download/8.16/Linux/nomachine_8.16.1_1_x86_64.tar.gz
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 25 Next › Last »
blackhole commented on 2022-07-04 21:26 (UTC)
aag commented on 2022-07-04 12:25 (UTC)
Getting a segfault in client with libva-2.15.0-1:
nxplayer.bin[5918]: segfault at d8 ip 00007f736444eff0 sp 00007f73517fa2e8 error 4 in libnxdixl.so[7f7364400000+cc000]
reverting it to 2.14.0-1 fixes the problem for me.
cdown commented on 2022-04-13 22:33 (UTC) (edited on 2022-04-13 22:37 (UTC) by cdown)
There are quite a few things that probably should be looked into in this package.
- The postinst should be created in an appropriate environment before the package is created, not after it is created. If nxserver can't handle that, the postinst steps should be performed manually.
- The postinst should not start or enable nxserver, this should be left up to the user. Starting and enabling services isn't an appropriate thing to do in a postinst.
- Packaged files are removed after packaging, which means
pacman -Qk
fails. - The installer isn't given the appropriate XDG environment, so it creates a root directory, /applications-merged:
% ls -l /applications-merged
total 4
-rw-r--r-- 1 root root 593 Apr 13 14:18 NoMachine-dir.menu
wereii commented on 2022-02-16 23:24 (UTC)
Just a FYI. If your session terminates/crashes instead of locking it might be caused by this
https://knowledgebase.nomachine.com/TR02T10468
I had screen blacking enabled in nxserver settings and currently it seems to crash Xorg on session switch/lock.
Ataraxy commented on 2022-02-10 06:51 (UTC) (edited on 2022-02-10 07:01 (UTC) by Ataraxy)
% sudo pacman -Qk nomachine
warning: nomachine: /usr/NX/etc/NX/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/localhost/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/localhost/server.cfg.sample (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/ (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxclient.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxnode.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxplayer.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/etc/NX/server/packages/nxserver.tar.gz (No such file or directory)
warning: nomachine: /usr/NX/nxserver (No such file or directory)
nomachine: 13 total files, 10 missing files
homerhsing commented on 2021-11-07 22:48 (UTC)
Hi! If the "nxserver" does not listen to port 4000, then edit file "/usr/NX/etc/server.cfg", set "StartNXDaemon" to "Automatic", set "EnableFirewallConfiguration" to "1", then restart "nxserver". The problem should be fixed then.
parkerlreed commented on 2021-09-30 06:21 (UTC)
Disregard. I had set the service to manual start (within the GUI settings) forever ago, uninstalled, and it remembered upon reinstalling.
parkerlreed commented on 2021-09-21 21:40 (UTC)
@galvez_65 Still nothing relating to 4000 :(
$ sudo netstat -tulpn | grep nx
tcp 0 0 127.0.0.1:7001 0.0.0.0:* LISTEN 2636/nxnode.bin
tcp 0 0 127.0.0.1:22171 0.0.0.0:* LISTEN 2582/nxserver.bin
tcp 0 0 127.0.0.1:12001 0.0.0.0:* LISTEN 2636/nxnode.bin
tcp 0 0 127.0.0.1:25001 0.0.0.0:* LISTEN 2658/nxclient.bin
tcp6 0 0 ::1:7001 :::* LISTEN 2636/nxnode.bin
udp 8448 0 192.168.1.172:5353 0.0.0.0:* 2582/nxserver.bin
udp 0 0 0.0.0.0:5353 0.0.0.0:* 2582/nxserver.bin
udp 1280 0 0.0.0.0:46956 0.0.0.0:* 2631/nxexec
galvez_65 commented on 2021-09-21 21:11 (UTC)
@parkerlreed I ran sudo netstat -tulpn to list it. Interesting when I run sudo netstat -atu (which is supposed to list open ports) it's not listed
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