LinuxQuestions.org Member Success StoriesJust spent four hours configuring your favorite program? Just figured out a Linux problem that has been stumping you for months?
Post your Linux Success Stories here.
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.
Recently I updated Crux to version 3.4 and then did a quick ports update. There was just one library to be updated (libidn) plus Imagemagick. The next time I logged into Crux, claws didn't work and neither did libreoffice. A quick ldd showed that they were linked to the old libidn-11 whereas I now had libidn-12. The culprit turned out to be gnutls, so I rebuilt that and the problem seemed to be solved.
But then I discovered that my Brother laser printer had also stopped working (though it still worked in Debian). Cups did not see any error or blockage so the problem had to be in the filter between cups and the printer. This is a bash script that invokes various small 32-bit proprietary programs. I ldd'd all the programs and they were linked correctly to /lib32/libc and /lib32/ld-linux.so. Everything looked fine, it just didn't work.
I modified the script so that it would create a debug file and looked in that, but still nothing sprang out. However it did list the arguments that cups had passed across, so I decided to try running the script by hand (as root) with those arguments. Well, I was desperate and I hoped standard error might show something that the log file didn't.
And it crashed with a message from ghostscript about not finding libidn-11! When I ldd'd /usr/bin/gs, it was linked to the new libidn via gnutls but also to the old one directly. That was what was causing the problem, not the Brother software at all. I rebuilt ghostscript and now the printer works. You don't get that sort of fun with Windows!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.