I was wondering...
I've had this problem before, but today I finally tryed to fix it for
good. Sometimes when updating some fundemental packages (don't ask me
which one) the problem occurs. Today I upgraded to KDE 2.2 (non-BETA)
with rpmdrake. And it had conflicts with other packages (i.e. usermode,
msec, drakfont, etc... ) so I just upgraded them at the same time.
After doing this, things like gaim and vim and others will print
something like "...Unable to open shared library: ... : file not found".
And it won't print the filename that was not found either. Well,
previously I would just reinstall or upgrade gaim or vim to solve the
problem. And any other packages that I may use rarely or never would
still remain broken. Today I decided to fix it a little better.
I did a find on all directories that contain "*.so*" and took just to
dirname of it, then sorted uniquely.... Then I took these (25 or so)
paths and pasted them into /etc/ld.so.conf and re-ran ldconfig
Now everything works fine... I'm complaining because I don't know the
exact reason that upgrading these other packages would cause the libs to
not be found.
I understand that upgrading a package might replace an old .so with a
newer one and perhaps change the name, but then why would adding all
those paths help then if the file didn't exist anymore. Did upgrading
the package move the shared library to a new and previously unknown
directory? Should ld.so.conf come default with more non-application
specific paths in it?
I know I'm dealing with Cooker here, but when a newbie linux guy (not me
;) ) really wants/needs the latest KDE (because of it's increase
stabilty and/or new features) frustrasion could ensue, where it could
have easily been remedied if /etc/ld.so.conf had had more paths in it?
Could someone explain the problem, or heed my sugguestion (if it's even
a valid one)
Thanks,
Davy
