Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
By installing opera 7.11 on Red Hat 9, I got the error message
Failed Dependencies
libXm.so.2 is needed by opera-7.11-20030515.1
I searched the Web including LinuxQuestions. If I understand right, I need to copy libXm.so.2 to /lib or /usr/lib an then run ldconfig. But this did not help.
When I try ldconfig -p, the libXm.so.2 is in the list. But I get the same error message...
Do I do anything wrong?
Additionally, I can use ldconfig only if I'm logged on on the computer via ssh or telnet. If I try to launch it directly in Terminal, the "bash" says it don't know this command.
I described the bash problem in my first message - I cannot execute some commands,
e.g. ldconfig, when I'm working in Terminal directly on the machine. If I log on via telnet or ssh,
it does work.
Well, ldconfig is located in /sbin which is probably only in root's path. I'm guessing that you are ssh'ing as a regular user but you are root in the terminal. If you su while ssh'ing into the machine then you should be able to execute ldconfig.
I am a bit baffled myself as to why the path is correct via ssh but not through the terminal. Maybe a way to fix this issue is to make sure whenever you use the su command you do it like this:
su -
This way when you become root you will retain all the properties that root should have.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.