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#33552 - [libxcomp] [nxclient] missing required components in system NX directory

Attached to Project: Arch Linux
Opened by Angus McInnes (jib) - Friday, 25 January 2013, 01:07 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 23 March 2013, 15:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

When I start nxclient, it says "Unable to find one or more required components in your system NX directory. Please select a different path:"

This seems to be because it's looking for lib/libXcomp.so in the "system NX directory", which is /usr/lib/nx.

Adding a symlink to libXcomp.so in /usr/lib/nx/lib fixes the problem.

Looks like the libxcomp package previously provided this symlink, but was changed in this commit: https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/nx&id=416d18ab2b84ca4a0a0f74aedd9e20aac59e8514

Additional info:
nxclient 3.5.0.7-3
nx-common 3.5.0-5
libxcomp 3.5.0.17-3

I removed my .nx to ensure that this wasn't just a problem with my configuration files.

Steps to reproduce:
Run nxclient. When it's working correctly, you should get the "NX Connection Wizard" window. I am getting the "System NX directory" window.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 23 March 2013, 15:25 GMT
Reason for closing:  Won't fix
Additional comments about closing:  We're dropping NoMachine client from our repos now. They are unmaintained upstream and are insecure.
Comment by Andreas Radke (AndyRTR) - Friday, 25 January 2013, 09:14 GMT
Hm. I can't keep compatibility for the closed NoMachine client for all time. It has security issues. OpenNX is running fine for me not failing here.

Can you try to redefine the System NX directory to the /usr/lib/nx/ directory? Does it solve this?

I'd rather tend to drop the closed client pkg than to fix something for this ancient piece of crap.
Comment by Antonio (kokoko3k) - Friday, 01 February 2013, 15:27 GMT
symlinking lib/libXcomp.so to /usr/lib/nx works for me too, redefining the nx directory doesn't.
Comment by Michael Pusterhofer (feanor12) - Monday, 04 February 2013, 11:04 GMT
symlinking works thx

Loading...