Quote:
|
Quote:
Apparently this symlink is required to satisfy kmod Code:
bash-4.2# ldd kmod |
Quote:
|
Quote:
After installing "mozilla-nss-3.13.5-x86_64-1.txz" all *.so files I deleted before (see my edited post) is back: Code:
Installing mozilla-nss-3.13.5-x86_64-1... |
bash-4.2$ cat mozilla-nss-3.13.5-x86_64-1:
... Code:
usr/lib64/libplc4.so Why are only some of them getting that "ldconfig warning" ? |
Quote:
Just a hunch... maybe delete /etc/ld.so.cache and see if running ldconfig again rebuilds it without the warnings? |
Deleting ld.so.cache and running ldconfig again made no difference for me - except I only have three showing up. Not as many as eXpander.
|
Quote:
I found the problem, and I think it is because of Spotify. To be able to launch Spotify I had to do symlinks from /usr/lib64/seamonkey-2.10.1/ to /usr/lib64, the corresponded files match those from the ldconfig warnings: /usr/lib64/libnss3.so.1d /usr/lib64/libnssutil3.so.1d /usr/lib64/libsmime3.so.1d /usr/lib64/libplc4.so.0d /usr/lib64/libnspr4.so.0d So I deleted all the Spotify symlinks and re-added them but from /usr/lib64 instead of /usr/lib64/seamonkey-2.10.1/ because then I will generate the warnings again: ln -s /usr/lib64/libnss3.so /usr/lib64/libnss3.so.1d ln -s /usr/lib64/libnssutil3.so /usr/lib64/libnssutil3.so.1d ln -s /usr/lib64/libsmime3.so /usr/lib64/libsmime3.so.1d ln -s /usr/lib64/libplc4.so /usr/lib64/libplc4.so.0d ln -s /usr/lib64/libnspr4.so /usr/lib64/libnspr4.so.0d I dont understand though why one cannot make symlinks from seamonkey-2.10.1? Now, for the volumeicon thing, something about libnotify: Code:
bash-4.2$ volumeicon Anyway, thanks for help! *EDIT: Ok, I'm not sure what happened during the current updates,,, anyway I just symlinked again :): ln -s /usr/lib64/libnotify.so.4.0.0 libnotify.so.1 Now volumeicon works... |
Quote:
Pat, would you please add a note about this change in CHANGES_AND_HINTS.TXT? Thanks much if you do. :) |
I had forgotten about Spotify. I don't even use it, so I nuked it and all the symlinks. No more ldconfig errors. Thanks eXpander.
|
Quote:
slackpkg update slackpkg install-new slackpkg upgrade-all slackpkg clean-system You will never break your slackware. So IMO it's useless to get a changelog sorted |
Quote:
|
Quote:
|
Quote:
Code:
wget -qO- ftp://ftp.slackware.com/pub/slackware/slackware-current/ChangeLog.txt | grep ': Removed\.$' Code:
wget -qO- ftp://ftp.slackware.com/pub/slackware/slackware-current/ChangeLog.txt | grep ': Added\.$' |
Quote:
I asked Pat to mention this in the CHANGES_AND_HINTS.TXT file because right now the only Slackware related help with this change is this forum thread. There are plenty of references around the web and Slackware is not the only distro affected by this change. The CHANGES_AND_HINTS.TXT file is a good place to document this "abrupt" change. |
All times are GMT -5. The time now is 02:53 PM. |