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

Alex Aminoff aminoff at nber.org
Wed Apr 9 14:02:24 UTC 2014


On 04/08/2014 01:58 PM, Les Mikesell wrote:
> On Tue, Apr 8, 2014 at 12:46 PM, Urs Beyerle <urs.beyerle at env.ethz.ch> wrote:
>>>> Can't help with this problem (and I rarely use normal X myself...) but
>>> I think the nx libs are now maintained for or by the x2go project
>>> although they still work with freenx.
>>>
>> nx-libs-3.5.0.22-1.el6 belongs to x2go. See rpm -qi nx-libs-3.5.0.22-1.el6.
>> In my opinion, this package does not make sense for Freenx:
>>
>> rpm -ql nx-libs-3.5.0.22-1.el6
>>
>> /etc/ld.so.conf.d/nx-libs-i386.conf
>> /usr/lib/nx
>> /usr/share/doc/nx-libs-3.5.0.22
>> /usr/share/doc/nx-libs-3.5.0.22/COPYING
>> /usr/share/doc/nx-libs-3.5.0.22/LICENSE
>> /usr/share/doc/nx-libs-3.5.0.22/README
>> /usr/share/nx/SecurityPolicy
>>
>> Have you talked to the epel folks?
> 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. This is fine as long as that version 
of libX11.so is OK, but somehow it is not, and if you try to run 
something linked against it it complains of a symbol _XGetRequest not 
found. (You could argue whether this is a bug in the library that asks 
for that symbol or in libX11 that fails to provide it - but the standard 
libX11.so does not have this problem). I'm using libX11 as an example, 
there are several others that work the same way.

I am almost done testing using the RPM nx from repo nux that I found, 
which is 3.5.0-5 - it does not include any modification to ld.conf.so.d. 
I suspect that nx will still work without changing the library path for 
all executables, which is the answer to the question I originally asked.







More information about the FreeNX-kNX mailing list