[Linux] Local files do not play on Ubuntu 14.04

[#1]

Just to confirm this indeed worked! Combined with the previous solution, of course.

[#2]

I also combined the two solutions and got Spotify to play local files again! Many thanks for sharing your solutions. Would never have found it myself. Cheers!

[#3]

Thanks guys! This problem has been bugging me since I upgraded to 14.04 a few weeks ago and I haven't had time to figure out what was going wrong.

[#4]

Unfortunately every time I try and install FFMpeg through Synaptic it keeps getting broken packages, not sure why..

Any idea how long it'll take for Spotify to release an update that fixes it so we don't have to use deprecated libraries?

[#5]

One more thing in addition to woqer's post - once you force the ffmpeg version to the *saucy,, you should also block on that version.

I don't know if that's a separate option in Synaptic, but it is one in Muon (KDE/Kubuntu). This will stop the package manager from suggesting an update to the *trusty version.

[#6]

It should not be a problem to update ffmpeg, since what you need are the libraries not the ffmpeg package itself. So the problem is that if you update be careful to not autoremove the libraries (libavcodec53 and libavutil51 is what you need for spotify, maybe another one i'm missing)

[#7]

Hi. I did everything described above, but unfortunately ¨Force version¨"is not a selectable option in my package manager. How can I fix this, or is there another way to downgrade the package? Thank you for your help!

Cheers
Adriaan

[#8 · Accepted solution]

You might have very well forgotten to add the saucy repository, so your package manager can find only one version, and there's nothing to choose from.

Open your /etc/apt/sources.list and add this line: 

deb http://ppa.launchpad.net/jon-severinsson/ffmpeg/ubuntu saucy main 

 Then after doing sudo apt-get update (reload packages), you should be able to force the version in your package manager!

Otherwise if Latest Version reads as 7:0.10.11-1~saucy1 instead of 7:1.2.5-1~trusty1, then you might instead only have saucy one, and not trusty, with that you shouldn't really need to force versions.

[#9]

Thanks, that worked :)

[#10]

nothing here has worked for me... and now my system likely has some weird mix of saucy and trusty packages and I don't have a clear summary from this thread on which should be installed and which should not.