On Mon, Aug 20, 2018 at 8:17 PM, Alec Bayo <alec.b...@gmail.com> wrote: > Thanks for the reply Uli. Pasted output below > > Also, I was scratching my head some more after sending the previous email. > Would I run the two lines below to add these links manually? Or should I do > something more/else? > > ln -s /usr/lib64/libNX_X11.so.6 /usr/lib64/nx/X11/libX11.so.6 > ln -s /usr/lib64/libNX_X11.so.6.3.0 /usr/lib64/nx/X11/libX11.so.6.3.0
No, this would just be wrong! > $ ldd /usr/bin/nxagent > linux-vdso.so.1 => (0x00007ffe21fc2000) > libtirpc.so.1 => /lib64/libtirpc.so.1 (0x00007fa9d1cd4000) > libX11.so.6 => /lib64/libX11.so.6 (0x00007fa9d1995000) ... > libNX_X11.so.6 => /lib64/libNX_X11.so.6 (0x00007fa9d04c9000) An here's the problem. You should never see both libs in the ldd output. NX brings libNX_X11 but does not directly require it (linker-wise). Instead it requires a libX11.so.6. There must be a link in an NX related dir (I don't know the exact path on CentOS/RHEL and cannot look that up atm). That link must be named libX11.so.6 and point to libNX_X11.so.6. It is a trick that is required to ensure the other X11 libs (that are required by NX) who require a libX11.so.6 themselves use the NX variant of the lib instead of the one from the system (which would break NX). Now try objdump -x /usr/bin/nxagent. Grep for RUNPATH in the output and you will find the directory where to put the missing link. In that directory run ln -s /lib64/libNX_X11.so.6 libX11.so.6 This should fix it. It would be interesting to know the reason for the missing link. Uli _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
