Attempting to run kiso results in the following error message: kiso: error while loading shared libraries: libcdio.so.5: cannot open shared object: no such file or directory. .oOo. The version of libcdio installed: [ebuild R ] dev-libs/libcdio-0.75-r1 .oOo. Results of ls -l /usr/lib/libcdio* -rw-r--r-- 1 root root 150286 Jul 24 09:45 libcdio.a -rwxr-xr-x 1 root root 790 Jul 24 09:45 libcdio.la lrwxrwxrwx 1 root root 16 Jul 24 09:45 libcdio.so -> libcdio.so.6.0.0 lrwxrwxrwx 1 root root 16 Jul 22 20:58 libcdio.so.0 -> libcdio.so.0.0.1 -rwxr-xr-x 1 root root 61940 Jun 5 2004 libcdio.so.0.0.1 lrwxrwxrwx 1 root root 16 Jul 24 09:45 libcdio.so.6 -> libcdio.so.6.0.0 -rwxr-xr-x 1 root root 99884 Jul 24 09:45 libcdio.so.6.0.0 -rw-r--r-- 1 root root 29334 Jul 24 09:45 libcdio_cdda.a -rwxr-xr-x 1 root root 845 Jul 24 09:45 libcdio_cdda.la lrwxrwxrwx 1 root root 21 Jul 24 09:45 libcdio_cdda.so -> libcdio_cdda.so.0.0.0 lrwxrwxrwx 1 root root 21 Jul 24 09:45 libcdio_cdda.so.0 -> libcdio_cdda.so.0.0.0 -rwxr-xr-x 1 root root 24692 Jul 24 09:45 libcdio_cdda.so.0.0.0 -rw-r--r-- 1 root root 32308 Jul 24 09:45 libcdio_paranoia.a -rwxr-xr-x 1 root root 898 Jul 24 09:45 libcdio_paranoia.la lrwxrwxrwx 1 root root 25 Jul 24 09:45 libcdio_paranoia.so -> libcdio_paranoia.so.0.0.0 lrwxrwxrwx 1 root root 25 Jul 24 09:45 libcdio_paranoia.so.0 -> libcdio_paranoia.so.0.0.0 -rwxr-xr-x 1 root root 30968 Jul 24 09:45 libcdio_paranoia.so.0.0.0 .oOo. Setting a symlink results in an error. The current version of libcdio appears to not provide the needed functions for kiso. ln -s libcdio.so.6.0.0 libcdio.so.5 error: kiso: /usr/lib/libcdio.so.5: version `CDIO_5' not found (required by kiso)
Have you ran revdep-rebuild ? libcdio changes soname every now and then, and in such a cases all the software linked to it must be recompiled. This seems to be your case.
I did a revdep-rebuild to check that after I submitted the bug. It did not appear in the revdep-rebuild. .oOo. Results from rebuild: /usr/kde/3.2/bin/noatunsynaescope.bin /usr/kde/3.2/bin/noatuntippecanoe.bin /usr/kde/3.2/bin/noatuntyler.bin /usr/kde/3.2/bin/nspluginscan /usr/kde/3.2/bin/nspluginviewer /usr/kde/3.2/lib/kde3/noatunblurscope.so /usr/kde/3.3/bin/juk /usr/kde/3.3/bin/noatunsynaescope.bin /usr/kde/3.3/bin/noatuntippecanoe.bin /usr/kde/3.3/bin/noatuntyler.bin /usr/kde/3.3/lib/kde3/noatunblurscope.so /usr/kde/3.3/lib/libakode_xiph_decoder.so /usr/lib/bonobo/libnautilus-audio-properties-view.so /usr/libexec/nautilus-audio-view results from ebuilds: kde-base/kdeaddons-3.2.3 kde-base/kdeaddons-3.3.2 kde-base/kdebase-3.2.3-r1 kde-base/kdemultimedia-3.3.2 .oOo. The results are so clean because I did a revdep-rebuild about 6 weeks ago. :-) I still need to unmerge kde-3.2.3 and kde-3.3.2.
Try to re-emerge kiso, it should link to libcdio.so.6 now. What it's not clear to me is this: lrwxrwxrwx 1 root root 16 Jul 22 20:58 libcdio.so.0 -> libcdio.so.0.0.1 -rwxr-xr-x 1 root root 61940 Jun 5 2004 libcdio.so.0.0.1 you should not have these versions.
A little more info: kiso was last updated on: -rwxr-xr-x 1 root root 344640 Jul 13 18:44 /usr/bin/kiso From message # 1, you can see that libcdio was last updated on Jul 24. HOWEVER! Just on the off chance that kiso needed to be re-updated anyway, I emerged it again. -rwxr-xr-x 1 root root 344576 Aug 6 07:20 /usr/bin/kiso Now it works. :-) I'm _very_ surprised that revdep-rebuild did not pick this up! Thank you for your help. My problem is resolved, but there appears to be a problem someplace! If I can provide with any further info, please let me know.
(In reply to comment #3) > Try to re-emerge kiso, it should link to libcdio.so.6 now. > > What it's not clear to me is this: > > lrwxrwxrwx 1 root root 16 Jul 22 20:58 libcdio.so.0 -> libcdio.so.0.0.1 > -rwxr-xr-x 1 root root 61940 Jun 5 2004 libcdio.so.0.0.1 > > you should not have these versions. > Should I delete them?
equery depends libcdio results: app-cdr/kiso-0.8.2c media-video/vcdimager-0.7.22 I guess I should go ahead and re-emerge vcdimager as well.
Considering this fixed in the mean time (the problem with revdep is not isolated and it's already known iirc). Check whose are the extra libs with equery b, if they appear to be orphan, think about removing them and re-run revdep rebuild.
(In reply to comment #7) > Considering this fixed in the mean time (the problem with revdep is not > isolated and it's already known iirc). > > Check whose are the extra libs with equery b, if they appear to be orphan, > think about removing them and re-run revdep rebuild. > Files deleted. revdep-rebuild run - nothing different found. :-) Thanx
