Audacious not Playing MP3 files in Fedora core 6
 

Hi everyone

i have installed audacious in fedora core 6 by the following command

yum -y install audacious audacious-plugins-nonfree-mp3

when i play mp3 files i get a pop uup window saying that the right plugins have not been installed/enabled

All the plugins are enabled...
eventhen same error

I didnt get this errror when i first installed audacious in fedora
Now i have reinstalled fedora after trying ubuntu..
i got this error also when i have updated audacious in fedora

I installed with the livna repository

..i also tried enableing freshrpms also but same error...

Please help me to make audacious work properly

Bye

Your command is wrong, look at the one buddy here uses, he also has a Note regarding the command he uses.
http://www.mjmwired.net/resources/mj...a-fc6.html#mp3

I have tried with the command given in the link
...But i am getting same error

the following packages have been installed
-------
audacious-plugins-nonfree-tta-1.3.3-1.lvn6
audacious-plugins-1.3.3-1.fc6
audacious-1.3.2-1.fc6
audacious-plugins-nonfree-lame-1.3.3-1.lvn6
audacious-libs-1.3.2-1.fc6
audacious-plugins-nonfree-aac-1.3.3-1.lvn6
----------

the error message when playing wav/mp3 files is as follws

---------
Unable to play files.

The following files could not be played. Please check that:
1. they are accessible.
2. you have enabled the media plugins required.

--------


Please help me to make it work properly

bye

I don't know if you still have problems making audacious to work in FC6, but here is the command that I used to install the mp3/wma plugins.

These are from the livna repository.

The mp3's play fine, but I haven't gotten wma-files to play properly, neither in xmms nor audacious... :(

Hi zek

Is audacious working in your computer
what version of audacious are u using now??
I have seen in some page after googling that
audacious 3.2 is buggy and many other people had the same problem i had\..
so i thought of installing my previous version of audacious.....

Can you give me the link for the rpm file of old version of audacious plugins...for fedora core6

audacious-plugins-nonfree-mp3-1.2.5-1.lvn6

Bye

The version that is currently in the livna repository seems to be 1.3.2, as judged from

which returns

I installed mine from livna, where

returns

So that would be version 1.3.3. Don't know any links to rpms, sorry :(

I have a problem with Audacious, too.

The madplug.so mp3 plugin won't work with it.

Apparently I have audacious version 2.4.3 and the latest version of audacious-plugins-freeworld-mp3 is 2.4.0.

I cannot find audacious-plugins-nonfree-mp3 anywhere that's beyond version 1.4.5-1.

Any fix for this?

Find links to the still unpublished updates in one of these tickets:

https://bugzilla.rpmfusion.org/show_bug.cgi?id=1611#c2
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1616
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1618

Due to a weak dependency in 3rd party plugin packages, you should have waited for your MP3 plugin package provider to release updates. The Update Notes warned about this. Audacious 2.4.3 is ABI/API incompatible with 2.4.0 and older. For future updates of Audacious a stronger dependency has been made possible, but 3rd party plugin packages need to add such a dependency. Else Fedora could never release such updates for Audacious without breaking 3rd party plugins. (E.g. Audacious 2.5-alpha1 will break the Plugin API again.)

Well this audacious thing just auto-updates on its own, like everything else on my system that comes via yum. I had no idea this problem was coming...

Edited to add for newbs: problem solved. Get the src.rpm from the first link and do a "sudo rpmbuild --rebuild (file).src.rpm", go to /usr/src/redhat/RPMS or ~/rpmbuild/RPMS and (in fedora) do a "sudo yum install *.rpm" (you may also need the --gpgcheck in the yum command)

You could answer 'n' when Yum asks for confirmation. ;)

Plus, it's possible to yum downgrade, too.

Still this update could have gone much smoother.

RPM Fusion cannot build against Fedora Updates before they are released to the stable updates repository, and nobody could foresee that they would run into other infrastructure problems or would take so long to push the needed updates.

For future updates, a dependency like this will be available: