Hi, I’m using opensuse 13.1 and I was trying to copy a CD with k3b. But when the copying started, I got the error that k3b “cannot load libcdparanoia”, and nothing was copied. I checked with software management in the control center, and it does not find “libcdparanoia”.
If I try to rip a CD, k3b shows all the tracks with their song titles and authors, but when I click on “start ripping”, I get a message there may be a bug, and k3b closes.
I’ve also tried audex, but it doesn’t even seem to recognize the CD, whereas at least k3b recognized the CD with its tracks and titles.
HI wolfi, I have everything in the applications list you mentioned except cdrecord. I searched for it also in Yast, Yast says “no results”.
Cdparanoia is there, for sure. I was able to open it in a terminal, but I don’t know how to use it yet from the command line.
Here is my repo list:
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
If you have a package “libcdparanoia” you can avoid guessing (hopefully) about its origins by posting the “zypper info” about the package, eg
zypper info libcdparanoia
If that doesn’t describe a package’s origins but you firmly believed you installed libcdparanoia as part of a package and not compiled from source, you might return something useful with
Well, I found an answer to the copy problem – at least a workaround. A German-speaking user (also using 13.1) was having the same problem I was having, that “libcdparanoia would not load”, according to the message in k3b. The workaround answer was to change Copy Mode from “Normal” to “Clone”. It takes a little longer than normal copying, I think, but it works. My German is not that good, so I pasted the link into Google Chrome and asked for a translation.
Here is the link from the opensuse forum in German:
You don’t need cdrecord, if you have wodim.
wodim is a replacement for cdrecord, and is included in openSUSE instead of cdrecord for quite some time.
But that line was intended to find out whether you have some packages from previous openSUSE versions installed (maybe even cdrecord).
So please post the output.
Regarding the ripping, there is a bug in k3b 2.0.80 that causes it to crash.
Packman did contain that buggy version, but it was downgraded again to 2.0.2 in December because of that crash.
Maybe you still have 2.0.80 installed? That rpm line should show this.
If yes, right-click on the package in YaST and choose “Upgrade Unconditionally” to downgrade it to the 2.0.2 version in the Packman repo.
Yast, zypper up or patch, and PackageKit (your update applet) do NOT downgrade packages automatically.
Here is my repo list:
That looks ok.
Another question: When did you get that message about “libcdparanoia not found”? Immediately when starting the copy?
And what are your exact settings in the burn/copy dialog?
I tried a (normal) copy now and it seems to work fine here (with k3b 2.0.2 that is). But I aborted during the copy so I don’t really know whether it would have finished successfully.
PS: In the meantime I successfully copied an AudioCD twice (once with creating image files, once without, i.e. a direct copy).
No problems whatsoever with the normal copy mode (not clone).
I suppose you are trying to copy an AudioCD, right? Otherwise cdparanoia shouldn’t be used anyway.
That worked beautifully for copying an Audio CD. I noticed that in YaST, k3b 2.0.80 was the installed version, and 2.0.2 was marked as “devel”. Seems it should have been the other way around. Anyway, I followed your instructions, I used normal copy, and the tracks and song titles both appeared. Thank you.
I’m wondering whether Apper will keep trying to reinstall k3b 2.0.80 though?
Normal copy at first, then I tried clone copy, which worked, but did not pick up the song titles. Normal copy with 2.0.80 caused k3b to crash immediately after the message “libcdparanoia not found” occurred.
But where does YaST mark 2.0.2 as “devel”?
I don’t follow you there.
[edit]
I think I understand now what you mean.
There is a package called “k3b-devel”, yes (which would be at version 2.0.2 of course).
But that’s something completely different. That doesn’t imply anything whether this k3b version is a devel version or not.
It is only needed to write/compile plugins for k3b.
[/edit]
Again, 2.0.80 was available in Packman for some time, that’s why you have it installed.
Then those crashes were reported and therefore it got downgraded again to 2.0.2 in Packman.
Now there’s only 2.0.2 available in Packman, so YaST should have marked the package in red, which means that there’s only a lower version available than the one you have installed (or none at all).
But neither Apper, nor “zypper up”, “zypper patch” or YaST will automatically install the lower version. You have to force that.
I’m wondering whether Apper will keep trying to reinstall k3b 2.0.80 though?
There is no k3b 2.0.80 available any more. As I said, it got downgraded to 2.0.2 in Packman because of the crashes.
There still is 2.0.80 in KDE:Extra, but you don’t have that repo anyway, and Apper wouldn’t change your installed package to a version from another repo.
Normal copy at first, then I tried clone copy, which worked, but did not pick up the song titles. Normal copy with 2.0.80 caused k3b to crash immediately after the message “libcdparanoia not found” occurred.
So this apparently is another bug in 2.0.80. I was only aware of the crash when trying to rip a CD. Maybe they are related though.
Well, 2.0.80 is now gone from YaST. Yay! Only 2.0.2 files are showing for k3b. Except the last four, which are not installed. Three are marked “…debuginfo”, and one is marked “k3b-devel”.
By the way, I’ve now tested the ripping, and it is also perfect. Thanks so much again.