K3B system configuration problem

I’m getting an error message that I see others have gotten, but in my case, it does not appear that I have a MAD library installed. There are various installable packages I find in YaST in a search for MAD, so I’m uncertain about which is the right one. The closest one seems to be “libmad0.”

I’m running a new install of 11.2, and have the Packman repo enabled.

And, I’d like to know the correct package name for the “K3B MAD Mp3 decoder plugin” mentioned in the error so I can confirm if I’ve got that installed or not.

Any suggestions on correcting this error? Thanks in advance for the help.

Here’s my error message received at start-up of K3B:

Mp3 Audio Decoder plugin not found.
K3b could not load or find the Mp3 decoder plugin. This means that you will not be able to create Audio CDs from Mp3 files. Many Linux distributions do not include Mp3 support for legal reasons.
Solution: To enable Mp3 support, please install the MAD Mp3 decoding library as well as the K3b MAD Mp3 decoder plugin (the latter may already be installed but not functional due to the missing libmad). Some distributions allow installation of Mp3 support via an online update tool (e.g. SuSE's YOU).

I don’t have k3b-codecs installed, as is suggested in the restricted formats information. The only package so named in the repo is a ver. 1.91.0…, and the installed K3B application is ver. 1.68.0… . Can the codec package with a different version number be run, or do I have to replace K3B itself with the newer version (which is a release candidate version, which makes me a little squeamish). Thanks.

Just FYI, 1.68 is alpha or beta.

That was actually the most helpful reply I’ve ever gotten that didn’t answer any of my questions.

I checked the K3B project page and found that the default version that shipped with 11.2 is in fact an alpha version! So how much worse off could I be with an RC2? Pulled out openSuSE K3B, installed Packman K3B and k3b-codecs of matching ver. no. (and libmad0 was automatically pulled in), and error message is now gone.

Thanks, Akoellh!