Some scripts that I used to use seem to be broken. and the reason appears to be a lame error. Nothing has changed with my scripts since bringing them from my fedora core 3 box. The wav files are created and can be played back correctly. When I attempt to run the following command I get a "segmentation error" which results in lame not encoding anything to the target mp3 file.

$ lame -h filename.wav filename.mp3

I read in another post that simply uninstalling and re-installing lame will fix this problem. Unfortunately because of all of the dependancies that I have this is not an option for me.

Is anyone else experiencing this problem and know of a solution?

Thanks in advance.

The lame rpm has no unusual dependencies, other than a basic system in FC5:

You can remove it with:

rpm -e lame

Reinstall the Livna version.

Thanks for the response macemoneta,

I am running a Mythbox on the system and I'm afraid to break the entire mythsuite by doing this. When I checked the dependancies with yum it indicated that my entire mythsuite was dependant on lame and would be deleted if I removed lame. I would hate to ruin my perfectly installed mythtv system over something like lame.

If I run a rpm -e lame followed by a rpm -i lame will that break all of the dependacies that exist?

Also, I'm skeptical about the unistall - Reinstall fix. It doesn't really make alot of sense to me. Why would that fix anything?

Thanks again for the response.

Well i tried the rpm -e lame and this is the result.


Sorry in my last post I did not see that you suggested to re-install a livna version of lame. Is that know to fix some problems from the core version. I notice that the atrpm fedora version is lame-3.96.1-10.rhfc5.at.i386.rpm and the livna version is lame-3.96.1-6.lvn5.i386.rpm6c. Am I breaking my dependancy tree by doing this?

is there a way to force the un-install?

To remove, ignoring the dependency tree:

rpm -e --nodeps lame

You can then re-install with:

rpm -ivh lame-x.y.z.rpm

You can try different versions until you find one that works for your situation. The Linva version has always been stable for me.

Thanks for the Tip macemoneta but I don't want to break my dependancies over lame. What I have decided to do is switch over to oggenc until I can find the solution to the problem.

I'm curious... How do you think you will resolve a software bug, without replacing the software?

As long as you re-install lame after removing it, no dependecies should be broken. In general, rpms are built with '>=' revision checks, so that later software can be used. If the MythTV rpms are not built that way (without a very good reason), then you can open a packaging bug with the project.

You can verify your dependencies are OK with:

package-cleanup --problems

If you don't have that installed:

yum -y install yum-utils

Note that even a pristine FC5 install comes with some dependency errors.

macemoneta,

Thanks for holding my hand through this one. Simply removing and installing the exact same package from ATrpms did the trick. I didn't even need to do anything else it just worked afterwards.

Strange.

Thanks again.

This issue is resolved for me.