[FreeNX-kNX] nx-libs RPM on linux messes up normal X

Alex Aminoff aminoff at nber.org
Wed Apr 9 17:24:42 UTC 2014


On 04/09/2014 11:37 AM, Les Mikesell wrote:
> On Wed, Apr 9, 2014 at 9:02 AM, Alex Aminoff <aminoff at nber.org> wrote:
>
>>>> I have x2go from EPEL and freenx from CentOS installed on the same box
>>> and everything seems to work from either kind of session.   What
>>> should be broken?
>>>
>> The basic problem is that nx-libs-3.5.0.22 from epel comes with
>> /etc/ld.conf.so.d/nx-libs*.conf, which inserts /usr/lib64/nx into the search
>> path for libraries for ldconfig before the standard locations. So everything
>> that would normally be linked to /usr/lib64/libX11.so instead links to
>> /usr/lib64/nx/libX11.so.
> On my system with freenx and x2go:
>
> ls -l /usr/lib64/nx
> total 1084
>   drwxr-xr-x 2 root root 4096 Jan 29 11:02 bin
>   lrwxrwxrwx 1 root root 20 Jan 29 11:02 libXcompext.so.3 -> libXcompext.so.3.5.0
>   -rwxr-xr-x 1 root root 64936 Jan 5 21:59 libXcompext.so.3.5.0
>   lrwxrwxrwx 1 root root 21 Jan 29 11:02 libXcompshad.so.3 ->
> libXcompshad.so.3.5.0
>   -rwxr-xr-x 1 root root 45200 Jan 5 21:59 libXcompshad.so.3.5.0
>   lrwxrwxrwx 1 root root 17 Jan 29 11:01 libXcomp.so.3 -> libXcomp.so.3.5.0
>   -rwxr-xr-x 1 root root 985536 Jan 5 21:59 libXcomp.so.3.5.0
>   drwxr-xr-x 3 root root 4096 Jan 29 11:02 X11
>
>> This is fine as long as that version of libX11.so
>> is OK,
> Do you actually have a libX11.so there?  What package supplied it?
>

My "good" system has:
[root at client2c etc]# rpm -q -l nx-3.5.0-5.el6.nux | grep libX11
/usr/lib64/nx/libX11.so.6
/usr/lib64/nx/libX11.so.6.2
[root at client2c etc]# ls /etc/ld.conf.so.d/nx*
ls: cannot access /etc/ld.conf.so.d/nx*: No such file or directory

The configuration that was broken had:

[root at perlw2 conf]# rpm -q -l nx-libs-3.5.0.22-1.el6 | grep ld.so.conf.d
/etc/ld.so.conf.d/nx-libs-x86_64.conf

Unfortunately I can not now reconstruct precisely which RPM supplied 
/usr/lib64/nx/libX11.so; I think freenx-server had a dependency on 
nx-libs as well as nxagent, both from epel, and nxagent called for a 
bunch of additional RPMs.


Anyway, I tested my system with freenx-server.x86_64-0.7.3-21.el6.nux 
and nx-3.5.0-5.el6.nux and it appears to work great. So the answer to my 
original question is that no, NX does not require a change to the 
library search path for all binaries.

  - Alex




More information about the FreeNX-kNX mailing list