Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Current method to install the spotify rpm is based on the rpmfusion lpf-spotify-client package. Basically, this automates the process of downloading, building and installing a spotity rpm based on the official Debian packages.
EDIT: Bug reported (page 19), temporary work-around published.
EDIT: New solution based on the rpmfusion lpf-spotify-client package. Old method deprecated but still available.
EDIT: updated for new upstream release: 0.9.4.183.g644e24e.428-2
EDIT: Solution updated for 0.9.1.55.
EDIT: Downgrading procedure to 0.8.4 published
EDIT: Update header to include F19
EDIT: Solution updated for 0.9.0.133
EDIT: updating link
EDIT: new solution for 0.8.8 published.
Solved! Go to Solution.
Yes, it's broken since upstream does not provide 32-bit build. See [1]
We need info from spotify on if/when they are going to fix trhe 32-bit build in order to decide what to do. I have got no response so far using the the ways I have get feedback. So, we are sort of stuck at the moment. Note that [1] contains a work-around
--alec
Thanks the workaround solved the installation!
Thanks, just upgraded to F20 and the workaround also worked for me.
Just needed to install qt-x11
yum install qt-x11
to get around error when running spotify
missing libQtGui.so.4
When I try to do the LPF method, I get the following output:
➜ SOURCES DISPLAY= lpf update Rebuild and install failed build for spotify-client (0.9.4.183.g644e24e.428-8.fc20) (yes/no) [y]?y spotify-client: installing build dependencies spotify-client: downloading sources spotify-client: build failed spotify-client: build failed (use lpf log to view log) spotify-client: build errors spotify-client: exiting
If I run `lpf log`, I get the following output: http://pastebin.com/q8UB5XNS
I've tried every method I could find on google, and none of them work. Fedora 20. Can someone please help me? I really want to get this working on my computer.
Thanks so much!
Hi Abrambleninja, as Leamas mentioned the issue is that LPF doesn't yet support the new v0.9.10 x64 package. But there is a workaround.
Download the zip file from here:
https://github.com/leamas/spotify-make/archive/master.zip
Unzip it somewhere
In the directory you unzipped to, run the configure script
./configure
then use the script to download the deb package
make download
then run the install script (I did this as root, not sure if you have to)
sudo make install
This worked for me in F20.
Note: I did this from memory, so I may have messed up the order or some of the steps. Please use your own judgement if it seems wrong.
See the github page for full instructions:
Thanks so much, that worked!
This is the only thing that got it working for me on Fedora 20. Having audio skip issues, but I don't think it's related to the client as it was doing it with the web player and other things as well.
Thank you so much for the help with this. Big big big big thanks!
I'm sorry for this mess, but it's not much I can do about. It's basically an upstream error. However, I have reasons to beleive there will be a 32-bit build which will resolve this sooner or later.
NOTE: when you run 'make install as described above you should not use sudo, you should do it as a normal user. Actually, all sorts of trouble might happen if you have done this as root. You have been warned 🙂
Hi,
It seems like the filename for the files has changed in the spotify repository.
I'm Running F20, x86_64 by the way..
lpf-spotify-client is calling for filenames in the repository (http://repository.spotify.com/pool/non-free/s/spotify/ ) that doesen't exist which results in a 404:
Getting http://repository.spotify.com/pool/non-free/s/spotify/spotify-client_0.9.4.183.g644e24e.428-1_amd64.... to ./spotify-client_0.9.4.183.g644e24e.428-1_amd64.deb [..] curl: (22) The requested URL returned error: 404 Not Found Getting http://repository.spotify.com/pool/non-free/s/spotify/spotify-client_0.9.4.183.g644e24e.428-1_i386.d... to ./spotify-client_0.9.4.183.g644e24e.428-1_i386.deb [..] curl: (22) The requested URL returned error: 404 Not Found
The file "spotify-client_0.9.4.183.g644e24e.428-1_amd64.deb" isn't available in the archive, so I get why curl bails on that one.
However, the file "spotify-client_0.9.4.183.g644e24e.428-1_i386.deb" is present in the repo, so I don't have an idea about why curl gets a 404 on that one..
The following files are present in the repo:
spotify-client-gnome-support_0.9.11.27.g2b1a638..> 03-Jul-2014 08:37 2292 spotify-client-gnome-support_0.9.4.183.g644e24e..> 10-Oct-2013 08:41 2290 spotify-client-qt_0.9.11.27.g2b1a638.81-1_all.deb 03-Jul-2014 08:37 2278 spotify-client-qt_0.9.4.183.g644e24e.428-1_all.deb 10-Oct-2013 08:41 2276 spotify-client_0.9.11.27.g2b1a638.81-1_amd64.deb 03-Jul-2014 08:37 55061614 spotify-client_0.9.4.183.g644e24e.428-1_i386.deb 10-Oct-2013 08:41 41740148
How do i modify lpf to use the file "spotify-client_0.9.11.27.g2b1a638.81-1_amd64.deb" instead of the one specified?
I used @fat_kid 's workaround with success, skipping the sudo part tho.
The rpm is brolen since upstream does not provide 1386 builds. I have reasons to believe this eventually will be fixed , so I'm not updating this for now.
In the meantime there is https://github.com/leamas/spotify-make It's not a rpm package, but reasonable easy to use. If you make a user install, it will not interfere with upcoming rpm updates.
I am well aware of what you are stating, but is the x86_64 deb dependant on the i386 deb?
As I'm running spotify-make and it works just fine for me, It's not really an issue, I'm just curious on why the x86_64 version fails to install according to the log.
It fails because the rpm downloads a pinpointed source which matches it's version. This source is no longer available.
The RPM is done from single source rpm which creates both the i386 and x86 binarhy package. If I update the x86 package I will push an absolutely unnecessary build on the i386 users, which is kind of a pain. I could also split the package to two indepenet ones, but this involves a rather long review process; I suspect the 386 package will arrive before that review + other work is completed.
So. there are really no good alternatives. This way at least the i386 users are handled properly. In hindsight I could perhaps made other decisions. Also, I feel that the x86 hasn't slipped too long yet. But unless the 386 build shows up in a month or so we will need to split this package and update i386 and x86 indepently.
@leamas
Allright, now I'm following you.
I can agree with you that the approach to make different architectures dependant on each other isn't a optimal design decision, but It's easy to be a smartass afterwards..
If you want some help with testing with a independent x86_64 version, I wouldn't mind to assist you to get a release out if I can.
As a heads up, the build works on current fedora 21 but the install fails on its libgcrypt.so.11() dep. It's looking for libgcrypt.so.11 and the most recent version in f21 is libgcrypt.so.20 from libgcrypt-1.5.1-7.fc21
edit: fixing my bad spelling and clarified a little
I found a bug in the specfile that was the cause of the installation problem, bug with patch filed in rpmfusion.
Found a repo that works for x86_64, haven't tried i386 though..
# cat fedora-spotify.repo [fedora-spotify] name=Spotify digital music service baseurl=http://negativo17.org/repos/spotify/fedora-$releasever/$basearch/ enabled=1 skip_if_unavailable=1 gpgkey=http://negativo17.org/repos/RPM-GPG-KEY-slaanesh gpgcheck=1 [fedora-spotify-source] name=Spotify digital music service baseurl=http://negativo17.org/repos/spotify/fedora-$releasever/SRPMS enabled=0 skip_if_unavailable=1 gpgkey=http://negativo17.org/repos/RPM-GPG-KEY-slaanesh gpgcheck=1
And rpmfusion is updated since long. However, need to add the F21 branch, it's as of only available in F20 (that long...). Will do this Real Soon (tm).
EDIT: Done.
@leamas Thanks for adding the F21 branch, but it looks like the spec file currently in rpmfusion has a typo/mistake again. I've updated @seasickleader's bug with a new version of the patch based on their original patch but correcting the current mistake (libcrypt instead of libgcrypt). Could you push this through to the repo please?
Tried negativo's repo posted by mrrezli on Fedora 21 x86_64 with kernel 4.1.13-100.fc21.x86_64 . So far, so good.
Executed from terminal for debugging purposes, currently consuming around 512 - 600 MB of RAM: One song being played, notifications enabled, connected and sharing via Facebook.
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…