[SOLVED] nx3.5 and slackware 14.2

nass · 07-16-2016, 07:06 AM

Hi all,
this is already an issue for me since 14.1 (which is why I never upgraded to 14.1), but perhaps by now there exist some sort of solution/alternative.

So I wanted to ask how do you guys manage remote X sessions on your slackware servers? In an opensource manner of course (so nomachine's NX v4 is not an option).

the server components of nx (nx and freenx) are no longer available in the slackbuilds repositories (after slack 14.0) so this extremely valueable tool is no longer available.

I have attempted to compile x2go from slackbuilds but I remember that it did not work - it had never worked for me. So nx is still the only solution.

Obviously i am not even considering "ssh -Y" , but even *vnc solutions do not compare to nx algorithm so I wonder: what alternatives are there, which ones do you use?

Thank you all for your input.

brobr · 07-16-2016, 11:34 AM

Hi nass, as far as I use remote X sessions, this is with a x2go client for a x2go server run from a ubuntu install at work (They used to have nx3.5 on it but removed it and only use x2go now). For this I compiled both the x2go client plus some packages from nx, as suggested on this recent thread slackware-14-2-x86_64-multilib-sbo-x2goserver-x2goclient.

The x2go stuff on SlackBuilds is not the most recent; I compiled a newer x2go client (4.0.5) on current (14.2) without a problem.

Cheers,

Rob

kjhambrick · 07-16-2016, 12:03 PM

Nass --

On my do-list this weekend is to try to make x2goserver / x2goclient work as brobr described in the other thread.

In the meantime, I've built and installed the SBo nxclient-3.5.0-7.x86_64 SlackBuild and it works fine on my Slackware 14.2 64-bit + Multilib Machine.

-- kjh

nass · 07-18-2016, 04:55 AM

Good morning to both!
and thank you for the replies.
nx3.5 on slack64 v14.2 is certainly a relief and I shall surely use it initially.

Just to verify (and perhaps in the near future switch to the x2go altogether), I want x2go server to be running on slackware servers (not just x2go client). Right has been achieved by you guys?

Then Ι'll connect with x2go clients running on other slackware, debian* and even windows system.

brobr · 07-18-2016, 05:00 AM

Hi nass, I never worked with the server (or tried to install it); maybe kjh can give you the thumbs up there...

Rob

kjhambrick · 07-18-2016, 05:42 AM

Quote:

Originally Posted by nass

Good morning to both!
and thank you for the replies.
nx3.5 on slack64 v14.2 is certainly a relief and I shall surely use it initially.

nass --

Just to clarify ... I've ONLY installed nxclient-3.5.0-7.x86_64_SBo on my Slackware 14.2 64-bit + Multilib System.

The nxclient Slackbuild DOES work to connect from my 14.2 Multilib System to CentOS 5.x, CentOS 6.x and Slackware 13.37 nxservers.

Quote:

Just to verify (and perhaps in the near future switch to the x2go altogether), I want x2go server to be running on slackware servers (not just x2go client). Right has been achieved by you guys?

Then Ι'll connect with x2go clients running on other slackware, debian* and even windows system.

Yes, That's what I need as well.

Once I get it going, I'll have to install x2goserver on 60+ CentOS Boxes 'out in the wild' as well as come up with a Windows Client for our Customers to connect to their Headless Boxen.

I've not (

yet

) had any luck connecting via x2goclient.

I installed the nxserver components recommended by brobr but no joy connecting to a test CentOS x2goserver:

Code:

nxproxy
nxcomp

I've reattached brobr's SlackBuild here for your convenience.

I am wondering if my issue is due to conflicts because I have nxclient-3.5.0-7 installed.

I ran out of time over the weekend so I didn't have time to remove all traces of NX* and start from scratch.

I'll be off a few days later this week so I'll have time to play with it some more in the early mornings when I get up.

-- kjh

nass · 07-18-2016, 08:38 AM

oh bummer.
have you tried and failed to re-Slackbuild "nx" and "freenx" on one of your slackware servers ? or not need it at all?

kjhambrick · 08-01-2016, 08:19 AM

nass --

As of Saturday, 2016-07-30 HelLViS69 released an updated set of x2go packages on SBo for Slackware 14.2:

Code:

nx-libs-3.5.0.32
x2goclient-4.0.5.1
x2goserver-4.0.1.19

I removed the old version on my Slackware64 14.2 + Multilib system and reinstalled HelLViS69's packages.

Then I installed multilib and the following SBo Packages on a liveslak Plasma5 system:

Code:

perl-Capture-Tiny-0.40
perl-Config-Simple-4.58
perl-DBD-SQLite-1.48
perl-File-ReadBackwards-1.05
perl-Unix-Syslog-1.1

nx-libs-3.5.0.32
x2goclient-4.0.5.1
x2goserver-4.0.1.19

I still cannot connect from my main laptop ( slackware64 + multilib + x2goclient ) to the new liveslak x2goserver.

I AM able to run a remote xterm session via ssh:

Code:

$ ssh -Y -l live 192.168.0.192 xterm

And I did find some things that may need to be addressed in the new x2go packages:

1. the x2goserver README has a typo on the chown and chmod commands ( each needs a full path ).
2. /usr/bin/x2gopath - returned /usr/lib/ instead of /usr/lib64 on my multilib system ( see below )
3. the symlink: /usr/lib64/x2go/bin/x2goagent pointed at /usr/local/lib/nx/bin/nxagent instead of /usr/lib64/nx/bin/nxagent ( see below )
4. if you've got ANY `stty` commands that execute on non-interactive logins, x2goclient fails ( see below ).
5. turned on loglevel=debug in /etc/x2go/x2goserver.conf on the server-side

I fixed { 1..4 } 'by hand' on my system and I seem to be getting closer to starting a remote KDE Session but still no joy here.

The current state is that I get connected but the client hangs after making the ssh connection ( debug session is below ).

I've not reported this to HelLViS69 yet as I wanted to gather it all together before taking up his time.

When I've got the time, I'll try this again on a plain, unmodified liveslak64 + KDE4 Instance ... maybe that will work for me.

-- kjh

This is my modified /usr/bin/x2gopath script:

Code:

#!/bin/sh

# Copyright (C) 2007-2015 X2Go Project - http://wiki.x2go.org
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the
# Free Software Foundation, Inc.,
# 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
#
# Copyright (C) 2012-2015 Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de>
# Copyright (C) 2012-2015 Heinz-Markus Graesing <heinz-m.graesing@obviously-nice.de>
# Copyright (C) 2012-2015 Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
# Copyright (C) 2012-2015 Jan Engelhard <jengelh@inai.de>
#
# kjh added this
#
ArchTag=""
TheArch="$(Uname -m)"

[ "$TheArch" = "x86_64" ] && ArchTag="64"
#
# kjh added that
#
base="${0%/*}";
if test "$base" = "$0"; then
        base=".";
fi;

base=$(readlink -f "$base/..");

# The following section is subject to substitution by distro packaging tools.
# kjh inserted ${ArchTag} to the end of each instance of /lib/ in the case..esac
case "$1" in
        "base") printf '%s' "$base";;
        "lib") printf '%s' "$base/lib${ArchTag}/x2go";;
        "libexec") printf '%s' "$base/lib${ArchTag}/x2go";;
        "share") printf '%s' "$base/share/x2go";;
        "nx-x11") printf '%s' "$base/lib${ArchTag}/nx/X11";;
        "xinerama") printf '%s' "$base/lib${ArchTag}/nx/X11/Xinerama";;
        *) exit 1;;
esac;

if test -t 1; then
        echo "";
fi;

I manually fixed the /usr/lib64/x2go/bin/x2goagent symlink:

Code:

cd /usr/lib64/x2go/bin

ls -la x2goagent
# output:  lrwxrwxrwx 1 root root   29 Jul 31 05:29 x2goagent -> /usr/local/lib/nx/bin/nxagent
#
# note that /usr/local/lib/nx/bin/nxagent does not exist.  so I did this:

rm x2goagent
ln -s /usr/lib64/nx/bin/nxagent x2goagent

I added this if-block wrapper around my stty -echoctl and set -o vi commands in /etc/profile:
( eliminates an error like no stdout when x2goclient first connects to x2goserver )

Code:

if [[ $- == *i* ]]
then
 # echo "interactive shell '$-'" >&2   # testing
   set -o vi
   stty -echoctl
fi

Here is an `x2goclient --debug` session. Maybe you can see something I don't see ?

I get logged in OK but the session is greyed out and the only way out is to x-out of the client.

The sessions are left behind on the server and I have to kill them by hand.

Code:

$ x2goclient --debug &
[1] 29057
[konrad@kjhlt6 .ssh]$ x2go-INFO-1> "Starting X2Go Client..."
x2go-WARNING-1> "Non-fatal: can't load translator: :/i18n/x2goclient_c"
x2go-WARNING-1> "Trying to load language with lower preference, if existent."
x2go-WARNING-1> "Non-fatal: can't load translator: :/i18n/qt_c"
x2go-WARNING-1> "Trying to load language with lower preference, if existent."
x2go-INFO-3> "Started X2Go Client."
x2go-DEBUG-src/onmainwindow.cpp:513> "$HOME=/home/konrad"
x2go-DEBUG-src/onmainwindow.cpp:2202> Reading 3 sessions from config file.
x2go-DEBUG-src/sessionbutton.cpp:325> Creating QPixmap with session icon: ":/img/icons/128x128/x2gosession.png".
x2go-DEBUG-src/sessionbutton.cpp:325> Creating QPixmap with session icon: ":/img/icons/128x128/x2gosession.png".
x2go-DEBUG-src/sessionbutton.cpp:325> Creating QPixmap with session icon: ":/img/icons/128x128/x2gosession.png".
x2go-DEBUG-src/onmainwindow.cpp:2682> Creating QPixmap with session icon: '":/img/icons/128x128/x2gosession.png"'.
x2go-DEBUG-src/onmainwindow.cpp:2744> Starting session with key.
x2go-INFO-8> "Starting connection to server: 192.168.0.192:22"
x2go-DEBUG-src/onmainwindow.cpp:2783> Starting new ssh connection to server:"192.168.0.192":"22" krbLogin: false
x2go-DEBUG-src/sshmasterconnection.cpp:173> SshMasterConnection, host "192.168.0.192"port 22user "live"useproxy falseproxyserver ""proxyport 22
x2go-DEBUG-src/sshmasterconnection.cpp:210> Starting SSH connection without Kerberos authentication.
x2go-DEBUG-src/sshmasterconnection.cpp:214> SshMasterConnection, instance SshMasterConnection(0x264cc30)  created. 
x2go-DEBUG-src/sshmasterconnection.cpp:450> SshMasterConnection, instance SshMasterConnection(0x264cc30)  entering thread. 
x2go-DEBUG-src/sshmasterconnection.cpp:486> libssh not initialized yet. Initializing.
x2go-DEBUG-src/sshmasterconnection.cpp:797> cserverAuth
x2go-DEBUG-src/sshmasterconnection.cpp:812> state: 1

x2go-DEBUG-src/sshmasterconnection.cpp:1065> Trying to authenticate user with private key.

x2go-DEBUG-src/sshmasterconnection.cpp:1146> Authenticating with key: 0

x2go-DEBUG-src/sshmasterconnection.cpp:662> User authentication OK.
x2go-DEBUG-src/onmainwindow.cpp:2878> SSH connection established.
x2go-DEBUG-src/onmainwindow.cpp:3160> Continue normal X2Go session
x2go-DEBUG-src/sshprocess.cpp:199> Executing remote command via SshProcess object 0: "export HOSTNAME && x2golistsessions"
x2go-DEBUG-src/sshprocess.cpp:204> this=SshProcess(0x26210b0)  Running masterCon->addChannelConnection(this, ' "23185992-c175-49fe-a55d-16bea7c0a164" ', ' "bash -l -c 'echo "X2GODATABEGIN:23185992-c175-49fe-a55d-16bea7c0a164"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; export HOSTNAME && x2golistsessions; echo "X2GODATAEND:23185992-c" '); 
x2go-DEBUG-src/sshmasterconnection.cpp:1312> Locking SSH channel connection MUTEX.
x2go-DEBUG-src/sshmasterconnection.cpp:1314> Passing new channel conenction object to channelConnections.
x2go-DEBUG-src/sshmasterconnection.cpp:1316> Unlocking SSH channel connection MUTEX.
x2go-DEBUG-src/sshmasterconnection.cpp:1504> Creating new channel.

x2go-DEBUG-src/sshmasterconnection.cpp:1508> New channel:0x7fc98400e8e0

x2go-DEBUG-src/sshmasterconnection.cpp:1539> Executing remote: "bash -l -c 'echo "X2GODATABEGIN:23185992-c175-49fe-a55d-16bea7c0a164"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; export HOSTNAME && x2golistsessions; echo "X2GODATAEND:23185992-c175-49fe-a55d-16bea7c0a164";'"

x2go-DEBUG-src/sshmasterconnection.cpp:1562> New exec channel created.

x2go-DEBUG-src/sshmasterconnection.cpp:1666> EOF on channel 0x7fc98400e8e0; SshProcess object: 0
x2go-DEBUG-src/sshmasterconnection.cpp:1734> EOF sent.
x2go-DEBUG-src/sshmasterconnection.cpp:1738> Channel closed.
x2go-DEBUG-src/sshprocess.cpp:517> SSH finished: raw output (stdout): "X2GODATABEGIN:23185992-c175-49fe-a55d-16bea7c0a164
X2GODATAEND:23185992-c175-49fe-a55d-16bea7c0a164
"
x2go-DEBUG-src/sshprocess.cpp:528> SSH finished: true - "" (0).
x2go-DEBUG-src/onmainwindow.cpp:3549> ""
x2go-DEBUG-src/onmainwindow.cpp:4100> Executing remote command: "X2GODPI=120 x2gostartagent 1800x1000 adsl 16m-jpeg-9 unix-kde-depth_24 us auto 1 D KDE both"
x2go-DEBUG-src/sshprocess.cpp:199> Executing remote command via SshProcess object 1: "X2GODPI=120 x2gostartagent 1800x1000 adsl 16m-jpeg-9 unix-kde-depth_24 us auto 1 D KDE both"
x2go-DEBUG-src/sshprocess.cpp:204> this=SshProcess(0x264b5d0)  Running masterCon->addChannelConnection(this, ' "95052ae6-c92a-459c-a1b7-24eacda52c0a" ', ' "bash -l -c 'echo "X2GODATABEGIN:95052ae6-c92a-459c-a1b7-24eacda52c0a"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; X2GODPI=120 x2gostartagent 1800x1000 adsl 16m-jpeg-9 unix-kde-dep" '); 
x2go-DEBUG-src/sshmasterconnection.cpp:1312> Locking SSH channel connection MUTEX.
x2go-DEBUG-src/sshmasterconnection.cpp:1314> Passing new channel conenction object to channelConnections.
x2go-DEBUG-src/sshmasterconnection.cpp:1316> Unlocking SSH channel connection MUTEX.
x2go-DEBUG-src/sshmasterconnection.cpp:1504> Creating new channel.

x2go-DEBUG-src/sshmasterconnection.cpp:1508> New channel:0x7fc98400e8e0

x2go-DEBUG-src/sshmasterconnection.cpp:1539> Executing remote: "bash -l -c 'echo "X2GODATABEGIN:95052ae6-c92a-459c-a1b7-24eacda52c0a"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; X2GODPI=120 x2gostartagent 1800x1000 adsl 16m-jpeg-9 unix-kde-depth_24 us auto 1 D KDE both; echo "X2GODATAEND:95052ae6-c92a-459c-a1b7-24eacda52c0a";'"

x2go-DEBUG-src/sshmasterconnection.cpp:1562> New exec channel created.

x2go-DEBUG-src/onmainwindow.cpp:1557> Close event received.

x2go-DEBUG-src/onmainwindow.cpp:1581> Quitting from tray icon and closing application.

x2go-INFO-6> "Closing X2Go Client ..."
x2go-DEBUG-src/onmainwindow.cpp:1410> Saving settings ...
x2go-DEBUG-src/onmainwindow.cpp:1419> Saved settings.
x2go-DEBUG-src/onmainwindow.cpp:1441> Waiting for the SSH connection to finish ...
x2go-DEBUG-src/sshmasterconnection.cpp:716> SshMasterConnection, instance SshMasterConnection(0x264cc30)  waiting for thread to finish. 
x2go-DEBUG-src/sshmasterconnection.cpp:1423> Disconnecting ...

x2go-DEBUG-src/sshmasterconnection.cpp:1434> Deleting channel connections.

x2go-DEBUG-src/sshmasterconnection.cpp:1734> EOF sent.
x2go-DEBUG-src/sshmasterconnection.cpp:1738> Channel closed.
x2go-DEBUG-src/sshmasterconnection.cpp:1442> Disconnecting session.

x2go-DEBUG-src/sshmasterconnection.cpp:1448> Deleting sockets.

x2go-DEBUG-src/sshmasterconnection.cpp:1455> All channels closed and session disconnected. Quiting session loop.

x2go-DEBUG-src/sshmasterconnection.cpp:720> SshMasterConnection, instance SshMasterConnection(0x264cc30)  thread finished. 
x2go-DEBUG-src/sshprocess.cpp:52> SshProcess destructor called.
x2go-DEBUG-src/sshprocess.cpp:52> SshProcess destructor called.
x2go-DEBUG-src/sshmasterconnection.cpp:727> SshMasterConnection, instance SshMasterConnection(0x264cc30)  finished destructor. 
x2go-DEBUG-src/onmainwindow.cpp:1443> SSH connection finished.
x2go-DEBUG-src/sshmasterconnection.cpp:744> libssh finalized.
x2go-INFO-7> "Finished X2Go Client closing hooks."
x2go-DEBUG-src/onmainwindow.cpp:526> Destroying X2Go Client's main window.
x2go-DEBUG-src/onmainwindow.cpp:529> Finished destructor hooks for X2Go Client's main window.

# Next-to-Last, this is what I found in /var/log/messages on the server side when I ran the x2goclient session above:

Code:

Aug  1 12:43:00 liveslak64 sshd[838]: Accepted publickey for live from 192.168.0.6 port 40188 ssh2: RSA SHA256:4oEcIcF4NsDwSf68lnvu/V+isbf+wAJNepnisBqDhLs
Aug  1 12:43:00 liveslak64 /usr/bin/x2gostartagent: x2gostartagent called with options: 1800x1000 adsl 16m-jpeg-9 unix-kde-depth_24 us auto 1 D KDE both 
Aug  1 12:43:00 liveslak64 /usr/bin/x2gosessionlimit[894]: x2gosessionlimit has been called 
Aug  1 12:43:00 liveslak64 /usr/bin/x2golistsessions[898]: x2golistsessions has been called with options: --all-servers

# And Finally, this mess is in /var/log/debug on the x2goserver side ( 748 lines repeated at a VERY high freq.

I turned on debug mode in /etc/x2go/x2goserver.conf so I am not concerned about the high-freq logging at this point.

Code:

# grep '^Aug  1 12:4'  /var/log/debug |wc -l
748

# grep '^Aug  1 12:4'  /var/log/debug |head -4
Aug  1 12:43:00 liveslak64 /usr/bin/x2golistsessions[851]: x2golistsessions has been called with no option 
Aug  1 12:43:00 liveslak64 /usr/bin/x2gostartagent: client announced itself as ,,192.168.0.6'' 
Aug  1 12:43:00 liveslak64 /usr/lib64/x2go/x2gogetdisplays[921]: db_getdisplays called, server: liveslak64.kjh.home; return value:  
Aug  1 12:43:00 liveslak64 /usr/lib64/x2go/x2gogetports[943]: db_getports called, server: liveslak64.kjh.home; return value:  

# grep '^Aug  1 12:4'  /var/log/debug |tail -2
Aug  1 12:44:08 liveslak64 /usr/lib64/x2go/x2gogetdisplays[19431]: db_getdisplays called, server: liveslak64.kjh.home; return value:  
Aug  1 12:44:08 liveslak64 /usr/lib64/x2go/x2gogetports[19443]: db_getports called, server: liveslak64.kjh.home; return value:

brobr · 08-01-2016, 08:58 AM

Question, and I cannot tell whether it makes sense at this point, what desktop do you want to use -as client when logging on to the x2go server? In my experience (and that of others here at work), it seems best to use something with a low-overhead, like LXDE as session-type, to get a settled connection.

HTH,

Rob

kjhambrick · 08-01-2016, 09:13 AM

brobr --

I am running KDE4 on the Client Side and KDE Plasma5 liveslak64 + multilib on the server side.

EDIT1: So the -client on the server-side is KDE Plasma5

EDIT2: I believe the available DE set is limited on the liveslak instances so all I can invoke is KDE ...

This is where I wanted to simplify the server-side with a 'stock' liveslak64 KDE instance.

And ... I found another PATH problem in /usr/bin/x2goagent ... fixed the path the same as in x2gopath

-- kjh

Code:

#!/bin/bash

# Copyright (C) 2012 Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program.  If not, see http://www.gnu.org/licenses/.
#
# kjh added this
#
ArchTag=""
TheArch="$(uname -m)"

[ "$TheArch" = "x86_64" ] && ArchTag="64"
#
# kjh added that
#
NXAPP=x2goagent
NX_LIBS=/usr/lib${ArchTag}/nx               # kjh added ${ArchTag}
NX_LOCAL_LIBS=/usr/local/lib${ArchTag}/nx   # kjh added ${ArchTag} just for completeness( no such dir )

# make sure nxagent starts properly with pam_tmpdir.so being in use
NX_TEMP=${NX_TEMP:-/tmp}
export NX_TEMP

test -x $NX_LOCAL_LIBS/../x2go/bin/$NXAPP && export NX_LIBS=$NX_LOCAL_LIBS
test -x $NX_LIBS/../x2go/bin/$NXAPP && export NX_LIBS=$NX_LIBS

exec $NX_LIBS/../x2go/bin/$NXAPP "$@"

brobr · 08-01-2016, 09:30 AM

Hi Kjh, I noticed that it was Kde to kde; you can change session type in the client; you can get lxde from SBo; otherwise ponce maintains a set of packages you can get via

Code:

 
cd [your package directory] # with folder lxde
rm -r lxde/* #get rid of old packages
lftp -c 'open http://ponce.cc/slackware/slackware64-current/ ; mirror lxde'

kjhambrick · 08-01-2016, 11:18 AM

Thanks brobr.

I'll check that out !

-- kjh

nass · 08-22-2016, 04:22 AM

Hi @kjhambrick.
I was away the past few weeks. I am not ready to switch to 14.2 yet, but soon enough I'll try to set up a VM on 14.2 and try to use that as an x2goserver.
meanwhile my experience with the x2go mailing list has not been fruitful.

If you do try out a simpler desktop environment please let us know about it.
I will try with xfce and even fluxbox which is especially light.

kjhambrick · 08-22-2016, 04:48 AM

nass --

Thanks for reminding me about this issue.

Yes, I've been pretty busy with my real job too.

I did try several different DEs with x2go, including lxde as brobr suggested and none of them have worked for me from my Slackware64 + Multilib Laptop Client to connect to a stock Slackware64 + Multilib 14.2 VM as the Server.

I've about given up on x2go.

Not that I would recommend it for anyone else, but I did install nxclient 3.5.x on my Laptop because I need it for my job so I went the 'instant gratification' route.

The nxclient app on Slackware64 14.2 works just fine with our CentOS Boxes that run nxserver 3.5.x out in the world.

I've not yet tried to sanitize nxserver and nxnode versions 3.5.x for Slackware64 14.2 -- there were some library conflicts in /usr/NX/lib/ that caused some ldd issues on Slackware 14.2 when I installed a 'package' converted from RHEL RPM Packages via rpm2tgz.

It seems simpler for me to fix the abandoned NX 3.5.x stuff than to get x2go going which will require installing x2goserver on 60+ Customer's CentOS Boxes out there.

Anyhow ... that's where I left it.

I am interested in x2go. I would definitely be interested if you figure it out.

Thanks !

-- kjh

brobr · 08-22-2016, 04:57 AM

two remarks: 1) The x2go server I connect to at work (after they killed the nx-3.5 one) is ran from ubuntu; it's also developed on/for ubuntu. Maybe worth trying it from a VM running ubuntu and see whether that can be made to work? Maybe that helps to sort out where it goes wrong for slack....
2) I am no longer running multilib. Still my client works fine. Does the server need multilib at all or is this an extra layer needed for something else but is not relevant for this issue?

rob