I tried to install HAProxy 2.6.12 in TCP mode to do load balancing (round robin) between 2 NoMachine 8.16.1 ECS (Enterprise Cloud Server) accepting NX protocol (SSH-like). NoMachine is a remote desktop solution. I use 4 VM (Debian 12): - 1 NoMachine Client (NX or SSH) - 1 HAProxy - ECS 1 = 1st member of the cluster - ECS 2 = 2nd member of the cluster It's working but I get a server identity warning each time I connect to an ECS of the cluster. :( The RSA public keys of the 2 ECS of the cluster are not saved together in a file called "/home/my_user/.nx/config/hosts.crt". It seems that each time I connect to an ECS, its public key overwrites the key of the other ECS already in the hosts.crt file. I actually don't understand the logic of this behaviour. NB: ECS supports SSH protocol and it works like a charm, I get a server identity warning only the 1st time I connect to HAProxy (I see the public key of HAProxy server in /home/my_user/.ssh/known_hosts). Any solution at HAProxy level or is it a pure NX protocol (no more open source since 2008!) problem ? SSH could be an alternative to NX but it is less performant... Thanks! haproxy.cfg (a little bit messy ;) ) global #log /dev/loglocal0 #STP log 127.0.0.1:514 local0 info log /dev/loglocal1 notice chroot /var/lib/haproxy stats socket /run/haproxy/admin.sock mode 660 level admin stats timeout 30s user haproxy group haproxy daemon defaults logglobal #STP modetcp #STP #optionhttplog optiondontlognull timeout connect 5000 timeout client 50000 timeout server 50000 #STP frontend ecs-in mode tcp # HAProxy listening port bind *:4000 default_backend backend-ecs # redondant with default ? log global backend backend-ecs mode tcp balance roundrobin # ECS listening port # NO send-proxy : NO go-mmproxy server ecs1 172.16.104.175:4000 check server ecs2 172.16.104.178:4000 check #server ecs3 172.16.104.179:4000 check # redondant with section 'global' ? log 127.0.0.1:514 local0 info frontend ecs-in-ssh mode tcp # HAProxy listening port bind *:22 default_backend backend-ecs-ssh # redondant with section default ? log global backend backend-ecs-ssh mode tcp balance roundrobin # ECS listening port server ecs1 172.16.104.175:22 check server ecs2 172.16.104.178:22 check #server ecs3 172.16.104.179:22 check # redondant with section 'global' ? log 127.0.0.1:514 local0 info

I am trying to disable NX protection on my linux (6.8.11-686-pae) to run a program that I need to test. But after setting GRUB to disable it, I am still getting: dmesg | grep NX [ 0.000000] NX (Execute Disable) protection: active grep -m1 nx /proc/cpuinfo flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht nx rdtscp constant_tsc xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor lahf_lm abm 3dnowprefetch pti fsgsbase bmi1 avx2 bmi2 invpcid rdseed clflushopt arat md_clear flush_l1d arch_capabilities grep noexec=off /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.8.11-686-pae root=UUID=f7f891fb-a9b6-42e2-8480-43ead6c59728 ro noexec=off noexec32=off splash My /etc/default/grub is set like this: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR= lsb release -i -s 2> /dev/null Il echo Debian GRUB_CMDLINE_LINUX_DEFAULT=“” GRUB_CMDLINE_LINUX="noexec=off noexec32=off" And also checked while booting with the e key (to see the current boot options: noexec=off noexec32=off are in the right place.

I'd like to verify that the current system is using NX bit protection somehow. I know that this can be done by checking the initial lines in the dmesg output. But that's a rolling buffer, so I'm not always going to be able to do it on a long-running system. Is there another way to verify the NX usage? I can't see any relevant /proc file. I was thinking of checking the memory maps for the loaded modules (is the data section executable), but I can't find any place where I could get them from. I'm trying to check that with root privileges, but passively (I know you could write a module to do the check actively, but don't want to go that far).

I have a NVIDIA Xavier NX (aarch64) with a custom board. It worked well with 4.x kernel and Cboot. Now after migrating to 5.x kernel and UEFI it hangs on boot with the following error: "ParseGicMsiBase: cannot retrieve property 'msi-parent': FDT_ERR_NOTFOUND" I don't have prior experience working with device trees and my question is how can I start investigating this problem. I familiar with the general concept of device trees and how to compile and use them. My lack of knowledge is mainly in the specific properties and values inside the .dts/.dtsi files. I don't know how one decides which properties are needed in each node and what their suitable values. For that reason I don't know how to try and fix my issue. I'm working with a specific SoM and custom board but I think the needed steps and knowledge are general and valid for other cases as well. Because of my lack of experience with this subject I'll be happy to get an answer as much detailed as possible in order to start investigating the issue and learn this subject as well. Thank you very much.

First I had a problem with the printer and sharing files, after disabling both it is solved and no window error is shown. Then when I have tried to access from client the windows is fully black. How could I fix it? Before the black screen I get this error: I use Gnome in CentOS 7. Here you have details of my session: NXPROXY - Version 3.5.0 Copyright (C) 2001, 2010 NoMachine. See http://www.nomachine.com/ for more information. Info: Proxy running in client mode with pid '12960'. Session: Starting session at 'Thu Nov 10 14:37:43 2016'. Info: Connecting to remote host 'localhost:31003'. Info: Connection to remote proxy 'localhost:31003' established. Info: Connection with remote proxy completed. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Failed to read data from the X auth command. Warning: Generated a fake cookie for X authentication. Info: Using ADSL link parameters 512/24/1/0. Info: Using cache parameters 4/4096KB/8192KB/8192KB. Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'. Info: Using ZLIB data compression 1/1/32. Info: Using ZLIB stream compression 4/4. Info: Using cache file '/cygdrive/C/Users/quico/X2GO~1/cache-unix-kde-depth_32/S-08242B7859B5E7DE927D20CD213366AE'. Info: Forwarding X11 connections to display 'localhost:0'. Session: Session started at 'Thu Nov 10 14:37:44 2016'. Info: Established X server connection. Info: Using shared memory parameters 0/0K. In my Centos 7 I use Gnome Desktop. Here I leave how I have configured the session: If you need more info, in order to help me, let me know.

My host is Windows 10 64-bit. I have a raspberry pi that I do not have direct access to. Neither do I have access to the router it's connected to. I simply use SSH to connect to it. But, I need to change Port Forwarding, and to do that, I need to have access to a GUI. So I am using NoMachine. But whenever I try to do

/usr/NX/bin/nxserver --startsession

I get:

NX> 500 ERROR: Display cannot be empty.

I have found solutions for Xvfb but Raspberry Pi OS uses LXDE.

Xvfb :99 -auth /home/username/.Xauthority -screen 0 1024x768x24 DISPLAY=:99 /etc/NX/nxserver -startsession

(Source: [https://forums.nomachine.com/topic/launch-session-using-commandline-in-with-nomachine-5-ts](https://forums.nomachine.com/topic/launch-session-using-commandline-in-with-nomachine-5-ts)) How would I go about this in SSH using LXDE on a raspberry pi? ------ I apologize if nothing of what I'm saying makes sense.

I'd like to make a solution that let's me offer a single Linux GUI app of my choice, e.g an emulator, to be controlled by basically anyone on the internet, trough e.g browser-based VNC. So, i'd like to ask generally what my options are, and also for any recommendations. Some points of importance to me: - The user(s) can't be able to run any other app than the one(s) i've set it to run. - The user(s) can't be able to kill any other processes. *(the ability of quitting the app itself i guess would be impossible to prevent)* - If a user quits the app, either deliberate or accidental, it and only it, must restart automatically. Alternatively, restarting the session. - The user(s) can't be able to drop to shell in any way. - The user(s) can't be able to end the session. - The user(s) can't be allowed to write to any files or dirs, other than the ones necessary for the chosen app. - Remote gamepad control would be nice. Main safety concern would really be to prevent the solution from being used for any nefarious internet activities, since it will be running on a VPS. And i'd rather not have my VPS provider get a reason to yell at me. I'm guessing disabling certain key and keystroke combinations would be part of the solution. Or rather, enabling only certain inputs while disabling *all* other input that are not necessary for operating the app, throughout the running session. **In some way or another**. (any tips on *how to* best do that are appreciated) Love to hear anything what you guys can come up with as to how it could be done. Just some possibly related/useful notes: - https://unix.stackexchange.com/questions/472781/how-to-load-your-own-gui-app-without-the-rest-of-the-gui-in-linux - https://unix.stackexchange.com/questions/512356/is-there-any-way-to-launch-gui-application-without-gui - https://stackoverflow.com/questions/3240633/web-based-vnc-client - https://linux.die.net/man/1/xmodmap - https://unix.stackexchange.com/questions/9061/where-to-apply-xmodmap-for-systemwide-usage - https://en.wikibooks.org/wiki/Guide_to_X11/Starting_Sessions

On Ubuntu with kernel 4.16.7 I am writing a custom system call and, I want to set the NX bit of a specific Page Table Entry. So far I have this piece of code, where I am doing a page table walk to get the PTE I want and then try to set its NX bit: pgd = pgd_offset(mm, addr); if (pgd_none(*pgd) || pgd_bad(*pgd)){ printk("Invalid pgd"); return -1; } p4d = p4d_offset(pgd, addr); if (p4d_none(*p4d) || p4d_bad(*p4d)){ printk("Invalid p4d"); return -1; } pud = pud_offset(p4d, addr); if (pud_none(*pud) || pud_bad(*pud)){ printk("Invalid pud"); return -1; } pmd = pmd_offset(pud, addr); if (pmd_none(*pmd) || pmd_bad(*pmd)){ printk("Invalid pmd"); return -1; } ptep = pte_offset_map(pmd, addr); if (!ptep){ printk("Invalid ptep"); return -1; } pte = *ptep; if (pte_present(pte)){ printk("pte_set_flags"); printk("NX bit before: %d", pte_exec(pte)); // pte_set_flags(pte, _PAGE_NX); // printk("NX bit after : %d", pte_exec(pte)); printk("pte_clear_flags"); // pte_clear_flags(pte, _PAGE_NX); // Same as pte_mkexec() pte_mkexec(pte); printk("NX bit after : %d", pte_exec(pte)); page = pte_page(pte); if (page){ printk("Page frame struct is @ %p", page); } pte_unmap(ptep); } but it doesn't work. All the printk commands show the same result. Any insight?

On an otherwise untouched installation of Fedora 20 Security Lab, I'm trying to enable NX access so I don't have to use Windows and the vSphere console. I have to use SSH to reach the host, no other ports are open. I'm able to connect to other machines running CentOS and Scientific Linux under the same network conditions. I start by setting sshd to start on boot: systemctl enable sshd.service Then I grab freenx: yum install freenx-server Then the dependency for nxagent: yum install nxagent I then configure the nxserver via /etc/nxserver/node.conf: SSHD_PORT=22 ENABLE_PASSDB_AUTHENTICATION="1" ENABLE_SSH_AUTHENTICATION="1" DISPLAY_BASE=1000 ENABLE_PERSISTENT_SESSION="all" ENABLE_CLIPBOARD="both" ENABLE_PULLDOWN_MENU="1" COMMAND_MD5SUM="md5sum" Then from the /usr/libexec/nx directory: ./nxsetup --install --setup-nomachine-key This returns the following: Setting up /etc/nxserver ...done Generating public/private dsa key pair. Your identification has been saved in /etc/nxserver/users.id_dsa. Your public key has been saved in /etc/nxserver/users.id_dsa.pub. The key fingerprint is: 69:ad:50:52:59:d3:9d:93:77:d7:94:68:dc:eb:8b:92 root@localhost.localdomain The key's randomart image is: +--[ DSA 1024]----+ | .oo...o++| | .. ..+=o=| | . . . o+| | o o . | | . S . . | | o . . | | . . . .| | E . . | | . | +-----------------+ Setting up /var/lib/nxserver/db ...done Setting up /var/log/nx/nxserver.log ...done Adding user "nx" to group "utmp" ...done Setting up known_hosts and authorized_keys ...done Setting up permissions ...done ----> Testing your nxserver configuration ... Warning: Invalid value "APPLICATION_LIBRARY_PRELOAD=/usr/lib64/nx/libX11.so.6:/usr/lib64/nx/libXext.so.6:/usr/lib64/nx/libXcomp.so.3:/usr/lib64/nx/libXcompext.so.3:/usr/lib64/nx/libXrender.so.1". /usr/lib64/nx/libX11.so.6 could not be found. Users will not be able to run a single application in non-rootless mode. Warning: Invalid value "COMMAND_START_KDE=startkde" Users will not be able to request a KDE session. Warning: Invalid value "COMMAND_START_GNOME=gnome-session" Users will not be able to request a Gnome session. Warning: Invalid value "COMMAND_START_CDE=cdwm" Users will not be able to request a CDE session. Warning: Invalid value "COMMAND_XTERM=xterm" Users will not be able to request an xterm session. Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be able to use SAMBA. Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able to use SAMBA. Warning: Invalid cupsd version of "/usr/sbin/cupsd". Need version 1.2. Users will not be able to enable printing. Ignore if you use cups > 1.2 Error: Could not find 1.5.0 or 2..0 or 3..0 version string in nxagent. NX 1.5.0 or 2..0 or 3..0 backend is needed for this version of FreeNX. Warnings occured during config check. To enable these features please correct the configuration file. Testing your nxserver connection ... The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established. RSA key fingerprint is 1b:2d:0e:72:56:66:1a:f3:b5:97:66:93:c7:c4:e8:93. Are you sure you want to continue connecting (yes/no)? Warning: Permanently added '127.0.0.1' (RSA) to the list of known hosts. HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: not detected) NX> 105 quit Quit NX> 999 Bye <--- done Ok, nxserver is ready. PAM authentication enabled: All users will be able to login with their normal passwords. PAM authentication will be done through SSH. Please ensure that SSHD on localhost accepts password authentication. You can change this behaviour in the /etc/nxserver/node.conf file. Have Fun! I then grab the key from /etc/nxserver/client.id_dsa.key and add a new connection in NoMachine for Mac OS X. I set it as an SSH connection, under Advanced I select "Use the NoMachine login, add my key as the alternate server key, and attempt to connect. Every single time, I get: "The NoMachine service is not available or the access was disabled on host 10.30.5.22"

I'm trying to setup a server on an ArchBang OS. I get installation warnings/errors when I try to install FreeNX on an ArchBang OS. I also get an Authentication error that stops the NX server. I don't know if the two are related. Commands entered: sudo pacman -S openssh sudo sed -i 's/\#PermitRootLogin/PermitRootLogin/' /etc/ssh/sshd_config sudo sed -i '$a\AllowUsers folatt' /etc/ssh/sshd_config sudo systemctl enable sshd.socket sudo reboot yaourt -S nx-all sudo nxserver --status Last command output: NX> 900 Connecting to server ... NX> 204 Authentication to NX server failed. NX> 110 NX Server is stopped. NX> 999 Bye. Second last command output: NX> 723 Cannot start NX statistics: NX> 709 NX statistics are disabled for this server. NX> 700 WARNING: Error when trying to connect to NX server, error is: NX> 700 WARNING: nxsetup cannot validate the sanity of the current installation: NX> 700 WARNING: the current system or NX configuration could be broken. NX> 700 WARNING: If difficulties arise (for example sessions cannot be started), NX> 700 WARNING: it is advisable that you try to uninstall the NX server and the NX> 700 WARNING: NX client packages then install them again. NX> 700 WARNING: Search also the NoMachine Knowledge Base at the URL below: NX> 700 WARNING: http://www.nomachine.com/kb NX> 700 WARNING: for common errors encountered when performing a software update NX> 700 WARNING: and the related hints on how to solve them.. NX> 700 Installation of NX server was completed with warnings. NX> 700 Please review the install log '/usr/NX/var/log/install' NX> 700 for further details. NX> 700 Showing file: /usr/NX/share/documents/server/install-notices /usr/NX/var/log/install NX> 700 Starting: install node operation at: Wed May 11 11:14:09 2016. NX> 700 Autodetected system 'arch'. NX> 700 Install log is '/usr/NX/var/log/install'. NX> 700 Creating configuration in /usr/NX/etc/node.cfg. NX> 700 Running: /bin/cp -f '/usr/NX/etc/node-arch.cfg.sample' '/usr/NX/etc/node.cfg'. NX> 700 Result: OK. NX> 700 Inspecting local CUPS environment. NX> 700 Generating CUPS entries in: /usr/NX/etc/node.cfg. NX> 700 Running: ln -sf /usr/NX/bin/nxspool /usr/lib64/cups/backend/nx. NX> 700 Result: OK. NX> 700 Replacing: /usr/NX/etc/node.cfg. NX> 700 Running: /bin/cp -f /usr/NX/etc/node.cfg.tmp /usr/NX/etc/node.cfg. NX> 700 Result: OK. NX> 700 Deleting temporary file. NX> 700 Running: /bin/rm -f /usr/NX/etc/node.cfg.tmp. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/bin/nxuexec'. NX> 700 Result: OK. NX> 700 Running: chmod 555 '/usr/NX/bin/nxuexec'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/bin/nxuexec'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxkeyadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxkeyadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxkeyadd.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxtmpperm.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxtmpperm.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxtmpperm.sh'. NX> 700 Result: OK. NX> 700 CUPS support is disabled. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxuseradd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxuseradd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxuseradd.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxuserdel.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxuserdel.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxuserdel.sh'. NX> 700 Result: OK. NX> 700 Running: /usr/NX/bin/nxnode --validate. NX> 700 Result: OK. NX> 700 Running: /bin/mv '/usr/NX/etc/node.lic.sample' '/usr/NX/etc/node.lic'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/etc/node.lic'. NX> 700 Result: OK. NX> 700 Running: chmod 0400 '/usr/NX/etc/node.lic'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxlicense.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxlicense.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxlicense.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/tmp/.ICE-unix'. NX> 700 Result: OK. NX> 700 Running: chmod 01777 '/tmp/.ICE-unix'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/tmp/.X11-unix'. NX> 700 Result: OK. NX> 700 Running: chmod 01777 '/tmp/.X11-unix'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxmountadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxmountadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxmountadd.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxmountdel.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxmountdel.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxmountdel.sh'. NX> 700 Result: OK. NX> 700 Installation of version: 3.5.0-9 completed. NX> 700 Showing file: /usr/NX/share/documents/node/cups-info NX> 700 Bye. NX> 700 Installing: server at: Wed May 11 11:14:11 2016. NX> 700 Autodetected system: arch. NX> 700 Install log is: /usr/NX/var/log/install. NX> 700 Running: useradd -p '*' -d '/usr/NX/home/nx' -r nx. NX> 700 Result: OK. NX> 700 Command: echo '/usr/NX/bin/nxserver' | /usr/bin/chsh nx. NX> 700 chsh: Warning: "/usr/NX/bin/nxserver" is not listed in /etc/shells. Changing shell for nx. New shell [/bin/bash]: Shell changed.. NX> 700 Result: OK. NX> 700 Running: ssh-keygen -q -t dsa -N '' -f '/usr/NX/etc/keys/node.localhost.id_dsa'. NX> 700 Result: OK. NX> 700 Running: /bin/cp -f '/usr/NX/etc/passwords.db.sample' '/usr/NX/etc/passwords.db'. NX> 700 Result: OK. NX> 700 Running: touch '/usr/NX/etc/passwords.db.lock'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/passwords.db.lock'. NX> 700 Result: OK. NX> 700 Running: /bin/cp -f '/usr/NX/etc/administrators.db.sample' '/usr/NX/etc/administrators.db'. NX> 700 Result: OK. NX> 700 Running: touch '/usr/NX/etc/administrators.db.lock'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/administrators.db.lock'. NX> 700 Result: OK. NX> 700 Running: /bin/cp -f '/usr/NX/etc/guests.db.sample' '/usr/NX/etc/guests.db'. NX> 700 Result: OK. NX> 700 Running: touch '/usr/NX/etc/guests.db.lock'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/guests.db.lock'. NX> 700 Result: OK. NX> 700 Running: /bin/cp -f '/usr/NX/etc/profiles.db.sample' '/usr/NX/etc/profiles.db'. NX> 700 Result: OK. NX> 700 Running: touch '/usr/NX/etc/profiles.db.lock'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/profiles.db.lock'. NX> 700 Result: OK. NX> 700 Running: touch '/usr/NX/etc/users.db.lock'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/users.db.lock'. NX> 700 Result: OK. NX> 700 Running: touch '/usr/NX/etc/users.db'. NX> 700 Result: OK. NX> 700 Running: /bin/cp -fp '/usr/NX/home/nx/.ssh/restore.id_dsa.pub' '/usr/NX/home/nx/.ssh/default.id_dsa.pub'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/keys'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/keys/node.localhost.id_dsa'. NX> 700 Result: OK. NX> 700 Running: chown -R nx:root '/usr/NX/home/nx'. NX> 700 Result: OK. NX> 700 Running: chmod 0700 '/usr/NX/home/nx'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/var'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/var/db'. NX> 700 Result: OK. NX> 700 Running: chown -R nx:root '/usr/NX/var/db/closed'. NX> 700 Result: OK. NX> 700 Running: chown -R nx:root '/usr/NX/var/db/running'. NX> 700 Result: OK. NX> 700 Running: chown -R nx:root '/usr/NX/var/db/failed'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/passwords.db'. NX> 700 Result: OK. NX> 700 Running: chmod 0600 '/usr/NX/etc/passwords.db'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/passwords.db.lock'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/users.db'. NX> 700 Result: OK. NX> 700 Running: chmod 0600 '/usr/NX/etc/users.db'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/users.db.lock'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/guests.db'. NX> 700 Result: OK. NX> 700 Running: chmod 0600 '/usr/NX/etc/guests.db'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/guests.db.lock'. NX> 700 Result: OK. NX> 700 Running: chmod 0600 '/usr/NX/etc/administrators.db'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/administrators.db'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/administrators.db.lock'. NX> 700 Result: OK. NX> 700 Running: chmod 0600 '/usr/NX/etc/profiles.db'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/profiles.db'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/profiles.db.lock'. NX> 700 Result: OK. NX> 700 Running: touch /usr/NX/etc/nodes.db. NX> 700 Result: OK. NX> 700 Running: chown nx /usr/NX/etc/nodes.db. NX> 700 Result: OK. NX> 700 Running: touch /usr/NX/etc/nodes.db.lock. NX> 700 Result: OK. NX> 700 Running: chown nx /usr/NX/etc/nodes.db.lock. NX> 700 Result: OK. NX> 700 Running: touch /usr/NX/var/db/broadcast. NX> 700 Result: OK. NX> 700 Running: chown nx /usr/NX/var/db/broadcast. NX> 700 Result: OK. NX> 700 Creating configuration file: /usr/NX/etc/server.cfg. NX> 700 Running: /bin/cp -f '/usr/NX/etc/server-arch.cfg.sample' '/usr/NX/etc/server.cfg'. NX> 700 Result: OK. NX> 700 Running: /usr/NX/bin/nxserver --validate. NX> 700 Result: OK. NX> 700 Running: /bin/mv '/usr/NX/etc/server.lic.sample' '/usr/NX/etc/server.lic'. NX> 700 Result: OK. NX> 700 Running: chown nx:root '/usr/NX/etc/server.lic'. NX> 700 Result: OK. NX> 700 Running: chmod 0400 '/usr/NX/etc/server.lic'. NX> 700 Result: OK. NX> 700 Running: /usr/NX/bin/nxserver --validatenode. NX> 700 Result: OK. NX> 700 Running: chown -R nx '/usr/NX/var/db/stat'. NX> 700 Result: OK. NX> 700 Running: chmod 0770 '/usr/NX/var/db/stat'. NX> 700 Result: OK. NX> 700 Running: /bin/cp -p '/usr/NX/home/nx/.ssh/default.id_dsa.pub' '/usr/NX/home/nx/.ssh/authorized_keys2'. NX> 700 Result: OK. NX> 700 Cannot start NX statistics: NX> 701 NX statistics are disabled for this server. NX> 700 Running: /bin/mv -f /usr/NX/etc/server.cfg.tmp /usr/NX/etc/server.cfg. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxwtmpadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxwtmpadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxwtmpadd.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxcookiegen.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxcookiegen.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxcookiegen.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxhost.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxhost.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxhost.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxdpyinfo.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxdpyinfo.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxdpyinfo.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxwtmpdel.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxwtmpdel.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxwtmpdel.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxpasswd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxpasswd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxpasswd.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxconfigure.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxconfigure.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxconfigure.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxgroupadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxgroupadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxgroupadd.sh'. NX> 700 Result: OK. NX> 700 Running: chown root:root '/usr/NX/scripts/restricted/nxquotaadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod 744 '/usr/NX/scripts/restricted/nxquotaadd.sh'. NX> 700 Result: OK. NX> 700 Running: chmod u+s '/usr/NX/scripts/restricted/nxquotaadd.sh'. NX> 700 Result: OK. NX> 700 WARNING: Error when trying to connect to NX server, error is: NX> 700 WARNING: nxsetup cannot validate the sanity of the current installation: NX> 700 WARNING: the current system or NX configuration could be broken. NX> 700 WARNING: If difficulties arise (for example sessions cannot be started), NX> 700 WARNING: it is advisable that you try to uninstall the NX server and the NX> 700 WARNING: NX client packages then install them again. NX> 700 WARNING: Search also the NoMachine Knowledge Base at the URL below: NX> 700 WARNING: http://www.nomachine.com/kb NX> 700 WARNING: for common errors encountered when performing a software update NX> 700 WARNING: and the related hints on how to solve them.. NX> 700 Installation of NX server was completed with warnings. NX> 700 Please review the install log '/usr/NX/var/log/install' NX> 700 for further details. NX> 700 Showing file: /usr/NX/share/documents/server/install-notices NX> 700 Bye. /etc/ssh/sshd_config # $OpenBSD: sshd_config,v 1.98 2016/02/17 05:29:04 djm Exp $ # This is the sshd server system-wide configuration file. See # sshd_config(5) for more information. # This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin # The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options override the # default value. #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: # The default requires explicit activation of protocol 1 #Protocol 2 # HostKey for protocol version 1 #HostKey /etc/ssh/ssh_host_key # HostKeys for protocol version 2 #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_dsa_key #HostKey /etc/ssh/ssh_host_ecdsa_key #HostKey /etc/ssh/ssh_host_ed25519_key # Lifetime and size of ephemeral version 1 server key #KeyRegenerationInterval 1h #ServerKeyBits 1024 # Ciphers and keying #RekeyLimit default none # Logging # obsoletes QuietMode and FascistLogging #SyslogFacility AUTH #LogLevel INFO # Authentication: #LoginGraceTime 2m PermitRootLogin prohibit-password #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 #RSAAuthentication yes #PubkeyAuthentication yes # The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2 # but this is overridden so installations will only check .ssh/authorized_keys AuthorizedKeysFile .ssh/authorized_keys #AuthorizedPrincipalsFile none #AuthorizedKeysCommand none #AuthorizedKeysCommandUser nobody # For this to work you will also need host keys in /etc/ssh/ssh_known_hosts #RhostsRSAAuthentication no # similar for protocol version 2 #HostbasedAuthentication no # Change to yes if you don't trust ~/.ssh/known_hosts for # RhostsRSAAuthentication and HostbasedAuthentication #IgnoreUserKnownHosts no # Don't read the user's ~/.rhosts and ~/.shosts files #IgnoreRhosts yes # To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes #PermitEmptyPasswords no # Change to no to disable s/key passwords ChallengeResponseAuthentication no # Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes #KerberosGetAFSToken no # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication and # PasswordAuthentication. Depending on your PAM configuration, # PAM authentication via ChallengeResponseAuthentication may bypass # the setting of "PermitRootLogin without-password". # If you just want the PAM account and session checks to run without # PAM authentication, then enable this but set PasswordAuthentication # and ChallengeResponseAuthentication to 'no'. UsePAM yes #AllowAgentForwarding yes #AllowTcpForwarding yes #GatewayPorts no #X11Forwarding no #X11DisplayOffset 10 #X11UseLocalhost yes #PermitTTY yes PrintMotd no # pam does that #PrintLastLog yes #TCPKeepAlive yes #UseLogin no #UsePrivilegeSeparation sandbox #PermitUserEnvironment no #Compression delayed #ClientAliveInterval 0 #ClientAliveCountMax 3 #UseDNS no #PidFile /run/sshd.pid #MaxStartups 10:30:100 #PermitTunnel no #ChrootDirectory none #VersionAddendum none # no default banner path #Banner none # override default of no subsystems Subsystem sftp /usr/lib/ssh/sftp-server # Example of overriding settings on a per-user basis #Match User anoncvs # X11Forwarding no # AllowTcpForwarding no # PermitTTY no # ForceCommand cvs server AllowUsers folatt

If I run ssh -X server lxterminal I get a new terminal window open on my local desktop that I can then launch new applications on the server from (similarly to the old xrsh application, except using a secure tunnel so I don't have to be on the same trusted LAN). I have X2Go server installed on the same server, and the client on my local machine, but when I use it it runs a window manager on the remote server and creates a top-level window to contain all the windows created. How can I configure it to behave the same as just using ssh -X?

I have a centOS 6.5 server cat /etc/*elease CentOS release 6.5 (Final) I tried to install the NX on it using this document https://wiki.centos.org/HowTos/FreeNX This is how I install it because the latest package was moved from the web wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm rpm -ivh epel-release-6-8.noarch.rpm wget http://li.nux.ro/download/nux/dextop/el6/x86_64/nux-dextop-release-0-2.el6.nux.noarch.rpm rpm -ivh nux-dextop-release-0-2.el6.nux.noarch.rpm yum install freenx-server nxagent yum install opennx Loaded plugins: downloadonly, fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: centos.aol.com * extras: chicago.gaminghost.co * nux-dextop: li.nux.ro * updates: centos.pymesolutionsweb.com Setting up Install Process Package opennx-0.16-724.el6.centos.1.x86_64 already installed and latest version Nothing to do Then I install it on a Desktop environment (windows 7) on the machine in order to run the remote session. I installed the opnenx using the following link http://opennx.net/ I set it up as it is explained here https://wiki.centos.org/HowTos/FreeNX Then I try to connect but it always gives me the following message what should I do?

We're using freenx-server across login hosts where users access them via NoMachine clients from their end. Because of the many bugs associated with freenx and our budget not permitting the full commercial version, we end up with certain users having more than a few sessions as remnants when connections don't clean up after themselves upon termination (usually unintentional). Here's an example excerpt from /etc/nxserver.log: Display Type Session ID Options Depth Screen Status Session Name ------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------ 33091 unix-gnome 189E20515FC5624507CAF25C836FB426 --D--PSA 24 885x843 Suspended Connection to NXHost11 (user5) (Shadowed) 33053 unix-gnome 1DBD1E1131156842D72376675CE33E89 --D--PSA 24 1920x1123 Suspended Connection to NXHost11 (user5) (Shadowed) 33111 unix-gnome 385B87A23EA908C0B4C6D00806D063B6 --D--PSA 24 871x538 Suspended Connection to NXHost11 (user5) (Shadowed) 33082 unix-gnome 4D30B996528B752BFB1DE30240659230 --D--PSA 24 871x734 Running Connection to NXHost11 (user5) (Shadowed) 33057 unix-gnome 57904D3FF28785366D962CDA35CBC6D4 --D--PSA 24 871x555 Running Connection to NXHost11 (user5) (Shadowed) 33044 unix-gnome 6E338B9EE71D55DE4873ED83FCCB0AD9 --D--PSA 24 871x538 Suspended Connection to NXHost11 (user5) (Shadowed) 33112 unix-gnome 8B2C9442496D09EFA0B78A13239D4EA0 --D--PSA 24 871x696 Suspended Connection to NXHost11 (user5) (Shadowed) 33110 unix-gnome 8FD5158542B616E6B9B05B4E2425A6AF --D--PSA 24 871x831 Suspended Connection to NXHost11 (user5) (Shadowed) 33014 unix-gnome 933CD67071697FBDC63D435E954BC8D6 --D--PSA 24 871x538 Running Connection to NXHost11 (user5) (Shadowed) 33072 unix-gnome B07D38F59367CE02ECA445B6EBBF84A1 --D--PSA 24 1138x667 Running Connection to NXHost11 (user5) (Shadowed) 33000 unix-gnome B58A633707EEC0C59C8A51EC9D688D3C --D--PSA 24 1920x1123 Running Connection to NXHost11 (user5) (Shadowed) 33069 unix-gnome BB78D40014DE5CF2A706536FF76FCFD8 --D--PSA 24 871x802 Suspended Connection to NXHost11 (user5) (Shadowed) 33108 unix-gnome C57D24C4AAC14F839E0A8C6B6C83D24E --D--PSA 24 1920x1123 Suspended Connection to NXHost11 (user5) (Shadowed) 33070 unix-gnome F90462D7CCEC82D5DDDA1E8C2CCE78E4 --D--PSA 24 1168x909 Suspended Connection to NXHost11 (user5) (Shadowed) To remove the sessions so the user's client doesn't continually freeze up, we have to manually remove them from /var/lib/nxserver/db/running/ - but the formatting is not the same: [root@NXHost11 running]# pwd /var/lib/nxserver/db/running [root@NXHost11 running]# ls sessionId{095675CAD6805301A215278C29E186F5} sessionId{84A166F4F3D0B743357FA37751BDA786} sessionId{0FA3E7C0B2914C66B8E468BE646D88F7} sessionId{8B2C9442496D09EFA0B78A13239D4EA0} sessionId{104750C53E17F5B87A9BFBC1E966B8D7} sessionId{8CC40155C71AE6E7F73365DAFDCD2349} sessionId{14B7F108B0A13635B7D697B26427D856} sessionId{8ECBE26B9D5C10C44192C150FDA80158} sessionId{15782E405134B2CF3BD09821CC3DC55C} sessionId{8FADEDAE322A31585EB0DD8A30AB0285} sessionId{180CA97293F95E625F12894B78FE100B} sessionId{8FD5158542B616E6B9B05B4E2425A6AF} sessionId{189E20515FC5624507CAF25C836FB426} sessionId{92BCB8BA457267750FFE862EEB3C8CE6} sessionId{18F86BA13166B94D0A80F10E3D3F220F} sessionId{933CD67071697FBDC63D435E954BC8D6} sessionId{195E394D40C21178D0ED4E5198B90792} sessionId{9400C9D9D16CC0D4254DFAC45C9A52C9} sessionId{1CD93CE30AD76937710823D0FAE15828} sessionId{95DE940721837DF10BE3FEB1535DC78A} sessionId{1DBD1E1131156842D72376675CE33E89} sessionId{9A2A5A849295FC2EC4A9B7E27B53CBF7} sessionId{1E1B5C326321775CCA05F2752CE17A8B} sessionId{9D565E61FA3B1D81F9F1A0B185A0EC83} sessionId{1FE7FD8EC70DC99652F214A3B5E905D1} sessionId{A5877C91B948DFC24AF86EFB2495E527} sessionId{22FAD34C0CC63CD959204669D8FDD9F0} sessionId{A64443BB165B532521741D5D8F19EFAB} sessionId{272CF217D5E8F56973743F86CAAF94BC} sessionId{ABDC93271DF58FCE7DA7DBE7500C21B3} sessionId{27FF7291F20965E10272A39B1FB8E4DC} sessionId{AF6B1A42DD47C25FD176E60231A90DAD} sessionId{2E7F640462E924284B079E10CC0E2E23} sessionId{B07D38F59367CE02ECA445B6EBBF84A1} sessionId{330CB4473B1AF6C948F2BFB9BDD2BADB} sessionId{B2D860333DDD3B7FF35EA48BFF9ABD00} sessionId{385B87A23EA908C0B4C6D00806D063B6} sessionId{B42E37E4785B42342C4EB009D74B4EA0} sessionId{389242121CE6E206584C2A45E236ABFF} sessionId{B58A633707EEC0C59C8A51EC9D688D3C} sessionId{3C4884BB99ADFF1FA18B039E88A864D1} sessionId{B6C3CDE47C2371972A7536B854A931F4} sessionId{3FED31A80C56BA9B038A6A765AED0C38} sessionId{B779C01B1F1915E571B1639A481E9848} sessionId{400753DEC565BB0DB52ED904137C463F} sessionId{BB78D40014DE5CF2A706536FF76FCFD8} sessionId{421C53FC39AE9D79E60E6055D2FC7DE8} sessionId{C0740993AD5429567243033DD5451B0F} sessionId{42F76BBDCE57874C8E3A0109E61BE37B} sessionId{C0B5C4E91BFFC94A2ED8C399ADD264E4} sessionId{43DBB2733414428C80DD68FA87D7C5B7} sessionId{C57D24C4AAC14F839E0A8C6B6C83D24E} sessionId{46A37999D33B0D66026C48D6D9C7B90A} sessionId{C605F9961D8C4C6511CE11F375E2DAD2} sessionId{4D30B996528B752BFB1DE30240659230} sessionId{CD76B8B7119293B2CA6164D621BCA062} sessionId{57904D3FF28785366D962CDA35CBC6D4} sessionId{DAAA94C7D01E099A1D566AF0E44B23E4} sessionId{58BFD388FBED5D39EED5D03A6BEB83B7} sessionId{DBAE1C4AD9B0CEB956711384B9A4C503} sessionId{5DC416CBE36DD68259246F21C4D12C63} sessionId{DF866B06E27911C90130A4AC7F24E03C} sessionId{6284D3EE9771A085520C12C5C089CB63} sessionId{E112F0415D4B2B47D892FA16D83819AE} sessionId{63F6B34AF4DD407E46CAB8D52EE1B00D} sessionId{E767F74579682E357BCF9E8635658847} sessionId{64CD7EC1A6156DFD992DCF6AA0D3D959} sessionId{EB78959FD59424DAF2C965388A056AE3} sessionId{6D570D2998E544DD2E2B4F68A9185377} sessionId{ED560BFC6D38D0946AF3E0A453E8EBC2} sessionId{6E338B9EE71D55DE4873ED83FCCB0AD9} sessionId{EE11025659E3D66007357A870FB973AA} sessionId{70556E711755D613445D72F505F5ACAA} sessionId{EF819D2926EFF1DA0E0208578D282D28} sessionId{7706DEA73E98C5997D61CA6BE49D2313} sessionId{F1141CC7C189F45D4C6E1B5A805BA849} sessionId{7723BB4A0C5CCE18A67D5D64235357AC} sessionId{F5E6EC0AB1E015AE187CC30412291A70} sessionId{787D6CE3EBA641706F3E07DD61159B24} sessionId{F90462D7CCEC82D5DDDA1E8C2CCE78E4} sessionId{7BD83901652D8F26B9D4B128D0021344} sessionId{F904BF11478F62FF368ACAA9978F365B} sessionId{8100B0CADB1369EB9573E9B986758545} sessionId{F91EECDB9A7B9298763F3DB439205CFC} The other issue is that there are other users on the same host that have running NoMachine sessions I can't close, or it'd be easy enough to just rm the whole directory's worth of sessions. So, the question becomes, outside of manually removing each individual session ID: rm sessionId{pasteletternumbercombinationhere}, would there be an easier way to accomplish this without impacting other users' sessions? It doesn't appear as though ps can display info I can script as the "handler" mechanism of freenx takes ownership and all sessionID files are nx:nx and not the username.

I am running Fluxbox on an Ubuntu (14.04.5) NoMachine server. I have a very simple startup file: fluxbox="$HOME/.fluxbox" stderr="$fluxbox/stderr" (umask 077; > "$stderr") exec 2> "$stderr" setxkbmap de nodeadkeys exec ssh-agent fluxbox -verbose -log "$fluxbox/log" My problem is, that some process is modifying the xkbmap after I have set it in the startup file. The nodeadkeys variant gets lost about one second after I have set it. In order to track this behavior I wrote a trace program, which I start just in front of the setxkbmap command. This is my trace script. #! /bin/bash set -eu exec > $HOME/setxkbmap.trace n=${1:-100000} while ((n>0)); do date +"%T.%6N" setxkbmap -query n=$((n-1)) done When the script starts the variant is set: $ head -5 setxkbmap.trace 16:09:04.930663 rules: evdev model: evdev layout: de variant: nodeadkeys And after about a second the variant is missing: $ grep -A 5 nodeadkeys setxkbmap.trace | tail -5 16:09:05.864251 rules: evdev model: evdev layout: de 16:09:06.309512 How can I figure out, which process is changing the option?

My Setup ======== Client ------ - Ubuntu OS - Remmina Remote Desktop Client + remmina-plugin-nx Server ------ - Arch Bang OS - NoMachine for Linux - x86_64 - Chose fedora system for install My Userlist =========== [folatt@ArkOS_Dev log]$ sudo /usr/NX/bin/nxserver --userlist NX> 149 NX users list Username Redirected to Trusted for -------------------------------- ------------------------------ ----------------- folatt NX Server app = NX Client app = /usr/NX/var/log/nxerror.log Info: Handler started with pid 25064 on Sat May 14 17:34:12 2016. Info: Handling connection from 192.168.178.53 port 52378 on Sat May 14 17:34:12 2016. 25064 25078 17:34:20 989.611 DaemonGreeter/DaemonGreeter: WARNING! Read from FD#5 failed. 25064 25078 17:34:20 989.836 DaemonGreeter/DaemonGreeter: WARNING! Error 5, 'Input/output error'. Warning: Connection from 192.168.178.53 port 52378 failed on Sat May 14 17:34:20 2016. Warning: Connection error is 5, 'Input/output error'. Info: Handler with pid 25064 terminated on Sat May 14 17:34:20 2016.

I have a VPS which I've just reinstalled an OS on. The OS is CentOS 6 x32. I've exactly done the following: yum install wget nano firefox yum update yum groupinstall Desktop useradd wajed && passwd wajed visudo yum install nx freenx nxserver --adduser wajed cat /etc/passwd | grep ^nx cat /var/lib/nxserver/home/.ssh/client.id_dsa.key So, 1. I installed some software, updated the OS, installed Desktop. 2. Added a user and gave permissions. 3. Installed freenx. The result is that everything is good, and I could connect to the desktop, but there is no font... it's all boxes instead of letters. What could the problem be? Here is a screenshot: 

I'm looking for something to provide faster X11 fowarding than ssh -X provides. I do not need a full GUI session or the ability to drop/resume user sessions. I use NX regularly, but as far as I can tell, there's no way to use it without a virtual desktop where all the graphics get painted. (See: http://www.midwinter.com/~koreth/freenx-howto.html) VNC also seems to work only with a virtual desktop; same with X2Go. What I want is something I can run from a terminal that will only open a graphics window and draw to it when it needs to (like ssh -X does). Does this exist? Maybe I've just missed the proper way to do it in something like NX. I've done a ton of searching--I look into this every couple months without a solution--but maybe I'm just searching for the wrong thing. (Full use case: I'm running Sublime Text on a Linux desktop, and I connect to R running on a remote Linux server via SublimeREPL, which is more or less a terminal emulator within Sublime Text. Plotting things from R happens in a forwarded X window, and it's extremely slow using ssh -XC. I'd love to be able to send the terminal+graphics connection over NX, but NX doesn't seem to support single applications like this; it forces a full-blown user session with a virtual desktop.)

I am running Nomachine NX server on my Ubuntu 12.04, and I'm connecting from a Windows 7 machine using NX client. When I try to start VirtualBox, I get a permission denied error. The same user that I use to connect to NX session can obviously run VirtualBox just fine. How do I fix this?

After installinx nx server, gnome and setting run level 5 in inittab, nx can't connect to X server, but after killing Xorg it can. Looks like I have to accept the license to get rid of firstboot, but I only have ssh access. Initially: # init 3 # init 5 root 7642 7638 2 15:44 ? 00:00:01 /usr/bin/python2 /usr/sbin/firstboot root 7644 7642 1 15:44 ? 00:00:00 /usr/bin/Xorg :9 -ac -nolisten tcp vt6 -br # kill 7644 root 7784 7759 0 15:47 ? 00:00:00 /usr/libexec/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1 root 7787 7784 4 15:47 tty1 00:00:00 /usr/bin/Xorg :0 -br -verbose -audit 4 -auth /var/run/gdm/auth-for-gdm-r4nB6i/database vt1

When trying to connect to NX server with a **NX CLient for Linux** (installed from nxclient_3.5.0-7_amd64.deb) I get the following error. NX> 203 NXSSH running with pid: 8009 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 285 Setting the preferred NX options NX> 200 Connected to address: nnn.nnn.nnn.nnn on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey Received disconnect from nnn.nnn.nnn.nnn: 2: Too many authentication failures for nx However when I am trying to use NX plugin for **Remmina remote desktop client** (from remmina-plugin-nx) I get the following *different* error: NX> 536 ERROR: Reached the maximum number of allowed users on this server. The Remmina diagnostic log states that it is NXSERVER - Version 3.5.0-11 - LFE. Is it a problem on my (client) side, or on server side?