Hi,

I would appreciate some pointers to where I am going wrong with Amarok.

I recently upgraded from FC6 to Fedora7 and since doing so, Amarok will not play mp3 files.

In FC6, I had installed the xine engine and the extra stuff from the livna repo and mp3 files were playing nicely.

In Fedora 7, I installed a fairly normal, but comprehensive set of stuff and then added the things from livna that were recommended in the site:-
http://www.mjmwired.net/resources/mjm-fedora-f7.html

This was the same resource (but an earlier version, obviously) that got me going under FC6, so I hoped for a similar result. I installed the following stuff that relates to Amarok & mp3:-

amarok.i386 1.4.5-4.fc7 installed
amarok-extras-nonfree.i386 1.4.4-1.lvn7 installed
xine.i386 0.99.4-11.lvn7 installed
xine-lib.i386 1.1.6-2.fc7 installed
xine-lib-extras.i386 1.1.6-2.fc7 installed
xine-lib-extras-nonfree.i386 1.1.6-1.lvn7 installed
xine-plugin.i386 1.0-3.fc7 installed

When I configured Amarok, xine is the chosen engine and my mp3 collection was catalogued as before, but when I try to launch any mp3 file, it fails with the4 following message:-

"These media could not be loaded into the playlist:
file:///home/...../xxxx.mp3"

I also see the following message when I select the xine engine in the Amarok configuration screen:-

"The xine-engine claims it cannot play MP3 files.
You may want to choose a different engine from the Configure Dialogue, or examine the installation of the multimedia-framework that the current engine uses.
You may find useful information in the FAQ section of the Amarok HandBook."

Has anyone successfully configured Amarok in Fedora / (surely someone has?) and has anyone any ideas what I have done wrong/missed out?

BR

Pajamki

It has been working fine for me, here are the exact package I have installed:

I've also installed the w32codecs package, but I don't think that should matter, since it is mostly quicktime and wmv type stuff.

hollywoodb,

Thanks for the fast reply. Here's my print; looks the same but still no joy 8^(

[mick@linuxbox ~]$ yum list amarok\* xine\* | grep installed
amarok.i386 1.4.5-4.fc7 installed
amarok-extras-nonfree.i386 1.4.4-1.lvn7 installed
xine-lib.i386 1.1.6-2.fc7 installed
xine-lib-extras.i386 1.1.6-2.fc7 installed
xine-lib-extras-nonfree.i386 1.1.6-1.lvn7 installed


Any other ideas?

Only thing I can think of is if you copied or kept your settings from your previous Fedora install. I didn't keep any settings, I always start fresh with each install, so it is possible that something left over that doesn't work the same way now as it did then could be causing problems.

Well, I don't think so. I left my /home drive undisturbed, but I fresh-formatted my / drive as part of the F7 install, so unless there is some "naughtiness" in my user account data I can't think what else could be wrong. That shold have given me a clean sweep of all executables and libraries. Amarok doesn't seem to leave anything in my user area.

I don't want to go down the road of re-installing again; maybe I will try to log on under a fresh user account and see if it is the same there.

That's the first thing I would try...

FYI, KDE stores its settings in ~/.kde, and I believe that Amarok puts them there as well. Perhaps you could find the Amarok-specific bits and pull them out if a fresh user account works.

Hollywoodb,

OK, I made a quick test with a new user and Amarok fired up with its welcome screen, which I wasn't seeing as my normal user, even though I had uninstalled and reinstalled it.

I took this to be a confirmation of what you suggested about the stored settings, so I uninstalled Amarok and all the Fedora/Livna stuff to do with Amarok and xine extras. I then searched the whole disk for any *amarok* files and zapped them all. It was mostly config stuff in user directories under ~/.kde as you said.

I then reinstalled Amarok and the Livna stuff and started Amarok. This time I got the welcome screen and when I loaded an mp3 file, it worked.

Maybe there would have been a quicker/more elegant solution, but what the heck, it's working now!

Thanks for the helpful suggestions