Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16396 - [freenx,nxserver] trouble, Library error; "libXcomp.so.3"

Attached to Project: Arch Linux
Opened by Fred (pseudonomous) - Tuesday, 29 September 2009, 20:13 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 02 May 2010, 15:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I've been trying to install freenx on an old server to use for remote logins to my desktop, following largely the directions in the archwiki. I've run into the following problems:

I authenticate but after "downloading session information", my session fails, nxclient suggests running:

[code]"ssh -X myserver; /opt/NX/bin/nxnode --agent to test the basic functionality"[/code]

The first time I did this I found I was missing the "libXcomp.so.3" library. Here's the content I get in my session log:

/opt/NX/bin/nxagent: error while loading shared libraries: libXcomp.so.3: cannot open shared object file: No such file or directory
xrdb: No such file or directory
xrdb: Can't open display ':10'
$DISPLAY is not set or cannot connect to the X server

Searching the web found that in OpenSuse this file is provided by the nxcomp library, so I tried installing nxcomp from the AUR, but now I get:

/opt/NX/bin/nxagent: error while loading shared libraries: /usr/lib/libXcomp.so.3: file too short

In my session log in my user's ~/.nx/F-C-host-$DISPLAY-sessionnumber/ file, that is literally the entire log file.

Running nxagent either locally or through ssh -X now gives:
fred @ nibbler /opt/NX/share $ ssh -X bender /opt/NX/bin/nxnode
NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
^CKilled by signal 2.

It doesn't do anything until I send the "^C".

I should note that I was able to login with FreeNX exactly once after installing nxcomp, during with my server locked up shortly after finishing the KDE desktop screen (where by "locked up" I mean I couldn't ping it from the network, and I couldn't get it to accept input from a keyboard and it did not display anything on a locally connected monitor. It rebooted OK after a hard reset, though.)

Additional info:
* package version(s)
local/freenx 0.7.3-4
Free Software (GPL) Implementation of the NX Server
local/nx-common 3.3.0-3
NoMachine NX common package for client and server
local/nxcomp 3.3.0_4-2 (x2go alts)
NX compression library
local/nxserver 3.3.0-6
NoMachine NX is the next-generation X compression and roundtrip suppression scheme.
* config and/or log files etc.
I've attached the "details" from a failed session in nxclient.

An error w/ nxclient output similar to mine has been reported on the FreeNX mailing lists / Bug tracker, this user, however, is consistently able to log in eventually, and has trouble only with some number of initial attempts after a system reboot, I, howerver have not been able to login at all.

On thier bug filer it is:

[ Bug #16226 ] After reboot login fails 1st random number of times - always

that filer also runs Arch.

Steps to reproduce:

install freenx + nxserver, configure it, fail, install nxcomp from aur, fail in different ways. I've uninstalled nxcomp, and now get the same type of failures I used to.

I apologize if I should be reporting directly to the FreeNX project, or if the "bug" is merely my own incompetence.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 02 May 2010, 15:04 GMT
Reason for closing:  Fixed
Comment by Johanson (Johanson24) - Thursday, 26 November 2009, 20:02 GMT
Hey,

I ran into the same problem.

package: nxserver-3.3.0-6-i686

root@ws:~# /opt/NX/bin/nxagent
/opt/NX/bin/nxagent: error while loading shared libraries: libXcomp.so.3: cannot open shared object file: No such file or directory

i controlled the shared libs for this binary:

root@ws:~# ldd /opt/NX/bin/nxagent
linux-gate.so.1 => (0xb7826000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb777d000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb776f000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb7655000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7641000)
libm.so.6 => /lib/libm.so.6 (0xb761a000)
libXpm.so.4 => /usr/lib/libXpm.so.4 (0xb760b000)
libXcomp.so.3 => not found
libXcompext.so.3 => not found
libXcompshad.so.3 => not found
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb7601000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb75fc000)
libXtst.so.6 => /usr/lib/libXtst.so.6 (0xb75f7000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xb75f4000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb75ed000)
libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xb75ea000)
libc.so.6 => /lib/libc.so.6 (0xb74a3000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb748a000)
libdl.so.2 => /lib/libdl.so.2 (0xb7486000)
/lib/ld-linux.so.2 (0xb7827000)
libXi.so.6 => /usr/lib/libXi.so.6 (0xb7479000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb7476000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7470000)

ok - it seems like there are some libs missing.
At first i searched for the Xcomp lib, but didn't find the correct package.
A look to the installed files of the nxserver package gave me the missing libs.

root@ws:~# pacman -Ql nxserver
nxserver /opt/
nxserver /opt/NX/
nxserver /opt/NX/bin/
nxserver /opt/NX/bin/nxagent
nxserver /opt/NX/bin/nxauth
nxserver /opt/NX/bin/nxproxy
nxserver /opt/NX/lib/
nxserver /opt/NX/lib/libX11.so
nxserver /opt/NX/lib/libX11.so.6
nxserver /opt/NX/lib/libX11.so.6.2
nxserver /opt/NX/lib/libXcompext.so
nxserver /opt/NX/lib/libXcompext.so.1
nxserver /opt/NX/lib/libXcompext.so.3
nxserver /opt/NX/lib/libXcompext.so.3.3.0
nxserver /opt/NX/lib/libXcompsh.so
nxserver /opt/NX/lib/libXcompsh.so.3
nxserver /opt/NX/lib/libXcompsh.so.3.3.0
nxserver /opt/NX/lib/libXcompshad.so
nxserver /opt/NX/lib/libXcompshad.so.3
nxserver /opt/NX/lib/libXcompshad.so.3.3.0
nxserver /opt/NX/lib/libXext.so
nxserver /opt/NX/lib/libXext.so.6
nxserver /opt/NX/lib/libXext.so.6.4
nxserver /opt/NX/lib/libXrender.so
nxserver /opt/NX/lib/libXrender.so.1
nxserver /opt/NX/lib/libXrender.so.1.2.2
nxserver /opt/NX/man/
nxserver /opt/NX/man/man1

I added this library path to the search path from ld, so nxagent could find his libs.
echo "/opt/NX/lib" >> /etc/ld.so.conf

update library cache with:
root@ws:~# ldconfig

root@ws:~# ldconfig -p |grep libXcomp
libXcompsh.so.3 (libc6) => /opt/NX/lib/libXcompsh.so.3
libXcompsh.so (libc6) => /opt/NX/lib/libXcompsh.so

root@ws:~# ldd /opt/NX/bin/nxagent
linux-gate.so.1 => (0xb7845000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb779c000)
libXext.so.6 => /opt/NX/lib/libXext.so.6 (0xb7789000)
libX11.so.6 => /opt/NX/lib/libX11.so.6 (0xb769e000)
libz.so.1 => /usr/lib/libz.so.1 (0xb768a000)
libm.so.6 => /lib/libm.so.6 (0xb7663000)
libXpm.so.4 => /usr/lib/libXpm.so.4 (0xb7654000)
libXcomp.so.3 => /opt/NX/lib/libXcomp.so.3 (0xb7560000)
libXcompext.so.3 => /opt/NX/lib/libXcompext.so.3 (0xb7551000)
libXcompshad.so.3 => /opt/NX/lib/libXcompshad.so.3 (0xb7546000)
libXrender.so.1 => /opt/NX/lib/libXrender.so.1 (0xb753c000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb7536000)
libXtst.so.6 => /usr/lib/libXtst.so.6 (0xb7531000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xb752e000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb7527000)
libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xb7524000)
libc.so.6 => /lib/libc.so.6 (0xb73de000)
libdl.so.2 => /lib/libdl.so.2 (0xb73d9000)
/lib/ld-linux.so.2 (0xb7846000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb73b4000)
libjpeg.so.7 => /usr/lib/libjpeg.so.7 (0xb7380000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb728b000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb726d000)
libXi.so.6 => /usr/lib/libXi.so.6 (0xb725f000)


Now it works ;o)
So for me it doesn't look like a real "bug" more than a packaging "bug".
I also didn't know if this fix would harm other packages.

Comment by Tobias Powalowski (tpowa) - Thursday, 26 November 2009, 20:25 GMT
It doesn't harm, the freenx does all library path setting so this is not needed normally.

Loading...