Welcome to my website. I am always posting links to photo albums, art, technology and other creations. Everything that you will see on my numerous personal sites is powered by the formVistaTM Website Management Engine.

icon.linkedin.jpgicon.twitter.jpg

  • [SOLVED] Delete key not working with x2go server running XFCE
    03/17/2016 10:09AM

    I am working with a development environment whereby I VPN into an environment with an Ubuntu VirtualBox guest and then initiate an x2go client session to a developement workstation server that lives in the development environment.

    I had everythining working exactly as I wanted except that the Delete key did not work in the x2go session.

    Previously the xev output when pressing the delete key was:

    FocusOut event, serial 36, synthetic NO, window 0x2e00001,
        mode NotifyGrab, detail NotifyAncestor

    FocusIn event, serial 36, synthetic NO, window 0x2e00001,
        mode NotifyUngrab, detail NotifyAncestor

    KeymapNotify event, serial 36, synthetic NO, window 0x0,
        keys:  0   0   0   0   0   0   0   0   0   0   0   0   0   0 0   0
               0   0   0   0   0   0   0   0   0   0   0   0   0   0 0   0


    For the given user/X-session, go to Applications Menu -> Settings -> Keyboard

    Then under the 'Layout' tab, uncheck the 'Use system defaults' and specify the keyboard that you are using.  In my case it was:
        Keyboard Model: Generic 105-key (Intl) PC
        Keyboard Layout: English (US)

    NOTE:  the layout had TWO options that were both 'English (US)' and I selected the top-most item.
    Log out of the X session, which will kill the x2go session and then log back in to a new session and the delete key works as expected.

    xev output when pressing delete key is now:

    KeyPress event, serial 36, synthetic NO, window 0x3600001,
        root 0x146, subw 0x0, time 2229006870, (-615,43), root:(879,645),
        state 0x10, keycode 107 (keysym 0xffff, Delete), same_screen YES,
        XLookupString gives 1 bytes: (7f) "
        XmbLookupString gives 1 bytes: (7f) "
        XFilterEvent returns: False

    KeyRelease event, serial 36, synthetic NO, window 0x3600001,
        root 0x146, subw 0x0, time 2229006981, (-612,41), root:(882,643),
        state 0x10, keycode 107 (keysym 0xffff, Delete), same_screen YES,
        XLookupString gives 1 bytes: (7f) "
        XFilterEvent returns: False

  • How To Install NoMachine's NX Server and NX Client
    08/30/2012 10:50AM

    Following is a quick howto for installing the NoMachine free version of NXServer:

    . Make sure that you have a DNS entry for the hostname of your NX Server machine or an entry in the server's /etc/hosts file that points to it's IP.

    . rpm -i nxclient-3.5.0-7.x86_64.rpm
    . rpm -i nxnode-3.5.0-7.x86_64.rpm
    . rpm -i nxserver-3.5.0-9.x86_64.rpm

    . copy stock config file to server.cfg:
            . # cd /usr/NX/etc
            . # cp server.cfg server.cfg_oem
            . # cp server-redhat.cfg.sample server.cfg

    . edit config files:
            . /usr/NX/etc/server.cfg: ensure that the following values are set:
                    . EnablePasswordDB = "0"
                    . EnableStatistics = "0"
                    . EnableNodeMonitoring = "0"
                    . EnableUserProfile = "0"

            . /usr/NX/etc/node.cfg
                    . EnableSensor = "0"

    . generate SSH keys:
            . /usr/NX/bin/nxserver --keygen
            . use the key: /usr/NX/share/keys/default.id_dsa.key in the NX Client config when making a connection to your server

  • Solution for 'Server configuration error. Cannot log in. Please contact your system administrator' for NXServer/NXClient Session
    08/30/2012 10:38AM

    I am setting up a vm running CentOS 6.2 and want to be able to connect to it via NXClient.

    After doing the basic install and getting the key from the server I got the following error when trying to login on the client side:

    Server configuration error. Cannot log in.  Please contact your system administrator

    Looking at /var/log/messages on the server revealed the following (hostName is the name of the host for the machine, changed from the actual nameof the box):

    Aug 30 10:21:30 hostName NXNODE-3.5.0-9[12117]: ERROR: NX> 596 ERROR: NXNODE Ver. 3.5.0-9  (Error id eAE8C74) [eAE8C74] Logger::log nxnode 2963
    Aug 30 10:21:30 hostName NXNODE-3.5.0-9[12117]: ERROR: NX> 596 ERROR: create session: run commands [eAE8C74] Logger::log nxnode 2963
    Aug 30 10:21:30 hostName NXNODE-3.5.0-9[12117]: ERROR: NX> 596 ERROR: execution of last command failed [eAE8C74] Logger::log nxnode 2963
    Aug 30 10:21:30 hostName NXNODE-3.5.0-9[12117]: ERROR: NX> 596 last command: /usr/bin/xauth -v -f /home/rchapin/.nx/C-hostName-1004-3C32B952A4DB53BE56F707B06E917F71/authority source /home/rchapin/.nx/C-hostName-1004-3C32B952A4DB53BE56F707B06E917F71/scripts/authority [eAE8C74] Logger::log nxnode 2963
    Aug 30 10:21:30 hostName NXNODE-3.5.0-9[12117]: ERROR: NX> 596 exit value: 1 [eAE8C74] Logger::log nxnode 2963

    I realized after seeing this that I did not have a DNS entry for the hostName machine and xauth failed because it could not resolve it.

    In this case, I added a entry in /etc/hosts for the host name and was then able to fire up the NXClient session.

  • Fix For: Pango-WARNING **: failed to choose a font, expect ugly output and Other FireFox Errors
    11/29/2011 1:54PM
    $ firefox &
    [1] 1933

    $
    (firefox:1947): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'
    GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -? 1: Failed to get connection to session: /bin/dbus-launch terminated abnormally without any error message)

    (firefox:1947): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'
    GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -? 1: Failed to get connection to session: /bin/dbus-launch terminated abnormally without any error message)
    /usr/lib64/firefox-3.6/run-mozilla.sh: line 131:? 1947 Segmentation fault????? "$prog" ${1+"$@"}

    [1]+? Exit 139??????????????? firefox


    Should you see such an error when attempting to run FireFox from a remote terminal connecting to a local XServer (Xming, or similar) check the following:

    1. That the haldaemon is running
    2. That the dbus-x11 package is installed.? On RedHat based systems, you can yum install dbus-x11
    3. That you have fonts installed.? I did a bit of a brute force approach and ran: yum groupinstall 'Fonts'
Advanced Search

Categories

Archives