Originally Posted by volkerdi
That's a good question. In mozilla-nss, they aren't supposed to be symbolic links. They aren't here, but running ldconfig doesn't generate any warnings about that either.
Just a hunch... maybe delete /etc/ld.so.cache and see if running ldconfig again rebuilds it without the warnings?
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:
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:
volumeicon: error while loading shared libraries: libnotify.so.1: cannot open shared object file: No such file or directory
Anyone else having problem with volumeicon? Can you even compile it?
Anyway, thanks for help!
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...