MrBombastic

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: No keyboard input accepted after logging in #17599
    AvatarMrBombastic
    Participant

    Luckily I had a backup (from August 2017) of the NoMachine config file fs1:/usr/NX/etc/server.cfg, so I restored it and restarted /etc/init.d/nxserver and now the keyboard entry from the NoMachine session works again!!

    I guess I could have just removed NoMachine from the server and reinstalled it too, but this server.cfg file was much quicker to restore.

    In switching to an older version of NoMachine server.cfg I ran a diff and there are quite a few differences between them.  Would it be detrimental to leave the old server.cfg file with a newer version of NoMachine?

    in reply to: No keyboard input accepted after logging in #17596
    AvatarMrBombastic
    Participant

    I checked the processes with no NoMachine session running and it shows this:

    `fs1:/var/log # ps -ef | grep X
    nx        4361     1  0 Feb20 ?        00:00:01 /usr/NX/bin/nxserver.bin root 1 –daemon
    nx        4689  4361  0 Feb20 ?        00:00:00 /usr/NX/bin/nxd
    root     14717 61184  0 00:12 pts/1    00:00:00 grep X
    root     42442 42438  0 Feb20 tty7     00:00:13 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-jWX4wY/database -nolisten tcp vt7`

    The for comparison I started another NoMachine session and checked again…

    fs1:/var/log # ps -ef | grep X
    nx        4361     1  0 Feb20 ?        00:00:01 /usr/NX/bin/nxserver.bin root 1 –daemon
    nx        4689  4361  0 Feb20 ?        00:00:00 /usr/NX/bin/nxd
    nx       14006  4689  0 00:10 ?        00:00:00 /usr/NX/bin/nxserver.bin -c /etc/NX/nxserver –login -H 4
    nx       14028  4361  0 00:10 ?        00:00:00 /usr/NX/bin/nxserver.bin –virtualsession –sessionid 6BEDD558F1C8BC5E5E54CEF499E45FD2
    root     14043  4361  0 00:10 ?        00:00:00 /usr/NX/bin/nxexec –node –user root –priority realtime –mode 0 –pid 15
    root     14048 14043  2 00:10 ?        00:00:02 /usr/NX/bin/nxnode.bin
    root     14150 14048  0 00:10 ?        00:00:00 /usr/NX/bin/nxclient.bin –monitor –pid 14097
    root     14251 14097  0 00:10 ?        00:00:00 /usr/bin/gpg-agent –sh –daemon –write-env-file /root/.gnupg/agent.info /usr/bin/ssh-agent /bin/bash /etc/X11/xinit/xinitrc
    root     14254 14097  0 00:10 ?        00:00:00 /usr/bin/ssh-agent /bin/bash /etc/X11/xinit/xinitrc
    root     14372 14006  0 00:10 ?        00:00:00 /usr/NX/bin/nxexec –node –user root –priority realtime –mode 0 –pid 14 -H 4
    root     14379 14372  0 00:10 ?        00:00:00 /usr/NX/bin/nxnode.bin -H 4
    root     14659 61184  0 00:12 pts/1    00:00:00 grep X
    root     42442 42438  0 Feb20 tty7     00:00:13 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-jWX4wY/database -nolisten tcp vt7

    Out of frustration I ended up rebooting the server and still there was no ability to use the keyboard, just the mouse.

    Here is where it is even stranger, in a test NoMachine connection, as usual the mouse works perfectly, so I clicked to open Gedit (Gnome text editor) and was randomly pressing some keys in the vicinity of a,s,d,f, then suddenly I noticed a single ‘d’ in the Gedit document!?  Wow! but how?

    VNC TESTING:

    Interestingly connecting with VNC to displays :1 and :2 work fine.  VNC is started with xinetd on this server.

    I thought I was on a sure thing by rebooting the server, but alas no.  Is it worth me attaching a NXserver config file?

     

Viewing 2 posts - 1 through 2 (of 2 total)