Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 615576 - media-sound/spotify-1.0.49 requires libavcodec and libavformat major version at most 56 (52-56 should work) to play local files
Summary: media-sound/spotify-1.0.49 requires libavcodec and libavformat major version ...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Matthew Thode ( prometheanfire )
Depends on:
Reported: 2017-04-15 01:07 UTC by Barteks2x
Modified: 2017-07-23 02:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Barteks2x 2017-04-15 01:07:08 UTC
As said in the summary.

This means that local files won't play when using ffmpeg 3.x, which is required by some other packages. The same also applies to spotify 1.0.53 (no ebuild for it at the time I'm writing this).

I originally found the issue here: and attempted similar workaround (except without potentially breaking something by adding libraries outside of portage): I downloaded the proposed files and set LD_LIBRARY_PATH to point to that location when running spotify.

Reproducible: Always

Steps to Reproduce:
1. Install spotify with media-video/ffmpeg 3.x installed (I'm not sure which version of media-video/libav would be equivalent)
2. Get spotify 30-day premium trial
3. Add local files to your spotify library and try to play them
Actual Results:  
Spotify won't play these files and will show confusing message "This song is not available. If you have the file on your computer you can import it"

Expected Results:  
Spotify should play local files
Comment 1 Matthew Thode ( prometheanfire ) archtester Gentoo Infrastructure gentoo-dev Security 2017-07-23 02:50:26 UTC
I'm not even able to add the files to test, can you confirm it's still broken?  1.0.59 was just packaged.  Even if it is broken we can't really fix it I don't think since it seems to be a problem with the spotify client itself.