Bug 478993
| Summary: | When nomachine's nxclient is installed qtnx picks the wrong nxssh and breaks on libcrypto.so.* | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joachim Backes <joachim.backes> |
| Component: | freenx-client | Assignee: | Axel Thimm <axel.thimm> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | bugzilla, gwync, j, ngaywood |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 0.9-10.fc11 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-08-10 21:46:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Joachim Backes
2009-01-06 12:08:27 UTC
I'm getting this as well. It seems freenx-client contains a /usr/NX/lib/ with the libraries required to start qtnx (including the lib/libcrypto.so.0.9.8 mentioned above) but this directory is not searched. If I start qtnx with: export LD_LIBRARY_PATH=/usr/NX/lib; qtnx I get further. (In reply to comment #1) > I'm getting this as well. It seems freenx-client contains a /usr/NX/lib/ with > the libraries required to start qtnx (including the lib/libcrypto.so.0.9.8 > mentioned above) This is not correct: freenx-client does not provide a directory like /usr/NX/lib nor a lib as lib/libcrypto.so.0.9.8, but you have to install the nx package (beside free-nx) additionally. After having installed nx, I proceeded. > > If I start qtnx with: > > export LD_LIBRARY_PATH=/usr/NX/lib; qtnx > > I get further. This and bug 495467 are dups of each other. It's caused by having nxclient from nomachine installed alongside freenx-client. *** Bug 495467 has been marked as a duplicate of this bug. *** *** Bug 511937 has been marked as a duplicate of this bug. *** I'm not sure we can fix this on our side. The nxclient package forces its path, so that its nxssh is picked up which isn't setup correctly wrt to library paths. When nxclient uses it is does setup the environment to find these libraries correctly. E.g. nxssh from nomachines should either had not been in the $PATH or it should be able to work self-sustained. Both can only be fixed by the package's makers (nomachine). If anyone has a better idea, please reopen and comment here. Actually since nomachine's current package adds its path component to the end of the path, we are lucky and our nxssh is preferred when both are present. freenx-client-0.9-10.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/freenx-client-0.9-10.fc10 freenx-client-0.9-10.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/freenx-client-0.9-10.fc11 freenx-client-0.9-10.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update freenx-client'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-8008 freenx-client-0.9-10.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update freenx-client'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-8028 freenx-client-0.9-10.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. freenx-client-0.9-10.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. |