Package Details: spotify 1:

Git Clone URL: (read-only, click to copy)
Package Base: spotify
Description: A proprietary music streaming service
Upstream URL:
Keywords: music player
Licenses: custom
Submitter: gadget3000
Maintainer: AWhetter (NicoHood)
Last Packager: NicoHood
Votes: 2103
Popularity: 31.75
First Submitted: 2010-07-12 12:17
Last Updated: 2020-10-18 15:13

Pinned Comments

NicoHood commented on 2020-05-27 07:46

The package has been flagged out of date again. I want to remind, that we package the stable version of spotify, not the testing version. Stable versions can be found under the following link and have not been updated for a long time:

You can fix the GPG key issue by using:

curl -sS | gpg --import -

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

ClickTek commented on 2020-11-13 03:41

==> ERROR: Failure while downloading

--I kept getting this during the download but after spamming to keep trying it after the 5th time it just went through.

ajzcole commented on 2020-11-12 21:28

I get this error:

==> ERROR: /home/ajzcole/.cache/yay/gobject-introspection-git/gobject-introspection is not a clone of

Clean building does not fix the issue. Neither does a manual wipe of the cache.

EDIT: After installing gtk2 and gobject-introspection manually, everything was fine.

deafwhippin commented on 2020-11-10 23:53

I'm also having issues installing Spotify having followed all the suggestions below to add GPG keys. Here's the output I receive:

curl: (18) transfer closed with 124127740 bytes remaining to read
==> ERROR: Failure while downloading

EDIT (16/11/2020): Saw ClickTek's comment to continuously retry. Spotify finally pushed through and installed from cleanbuild.

TheIdealis commented on 2020-11-10 14:51

Just in case someone who has the gpg problems made the same silly mistake I did: I removed ~/.cache/yay/spotify but tried to install spotify-dev. After I removed both, I was able to install the program again.

renatoliveira commented on 2020-11-09 12:41

@techandy1 the difference between PGP and GPG is that one is the private solution developed by Symantec and the other one is the open source implementation. Since GPG is just an implementation of PGP, the correct naming would still be "PGP key".

I'm confused. Deleting the cache did not work for you? I would take a look into the previous 3 or 4 pages in the comments. Some commands were mentioned to clear the cache and reinstall the package.

As for anyone reading this: Spotify changed PGP keys used to sign the package, again. It is using a key that was used before, again. It is necessary to trust that key to install (or ignore signatures during install).

Anonymous comment on 2020-11-08 21:26

I am having issues with the GPG keys. None of the suggestions below have worked for me. I am still unable to update Spotify. Does anybody else have any suggestions?? I have also noticed that the validpgpkeys have not been updated in the PKGBuild file and also I thought it would be a validgpgkeys and not validpgpkeys????

voho commented on 2020-11-02 23:14

@kfallah, @bryanOmalley: I also had the same problem. Spotify warning about internet connectivity. I use WireGuard and NetworkManager.

EDIT: Running below should return full, and not limited like it does if I block the connectivity check. If it returns limited Spotify thinks it's offline.

$ nmcli networking connectivity check

Anyway, I started logging iptables and adding IP's that was being blocked on different interfaces.

What I found out is that apparently NetworkManager does it's own connectivity checking, which Spotify seems to care about.

On my machine:



NetworkManager uses that address for checking connectivity.

$ curl
NetworkManager is online

The strange thing was that in Wireshark I noticed that even if I was connected to VPN (WireGuard), requests to ( were being sent over both WireGuard and my normal network card.

My firewall/iptables blocked those requests that did not go over VPN. Strange that it would not only go over my VPN connection all the time.

Anyway, so the solution seems to be, either to disable NetworkManager's connectivity checking altogether. Or watching over you firewall / Wireshark to see if you have the same problem. And if so fixing your firewall.

For now I just allowed on my normal network interface, which iptables previously blocked which Spotify noticed.

iptables -A INPUT -i enp5c8 -s -p tcp --sport 80 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o enp5c8 -d -p tcp --dport 80 -j ACCEPT

And Spotify have been working since, time will tell if this was the problem.

jvloendersloot commented on 2020-11-02 13:52

curl not working anymore. Deleting the cache also didn't work.

bryanOmalley commented on 2020-11-02 10:35

@kfallah: I've got the same problem, but nobody talks about any fixes here. It's pretty annoying for me as well.

rojaro commented on 2020-11-02 10:25

I've ran into this problem as well with yay:

==> Verifying source file signatures with gpg...
    spotify- ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)
==> ERROR: One or more PGP signatures could not be verified!

Tried prety much everything from the previous comments, but nothing worked.

Deleting ~/.cache/yay/spotify before using yay fixed this issue for me.