Having trouble updating Spotify?

Posting this here in hopes of saving time for eternal newbs like myself.

The repo link to grab the .deb file seems to be broken for myself and some others. Below is the steps I've used to successfully update (rebuild) Spotify.

Firstly if you haven't added the edit build option to yay menu; do so now:
In terminal enter yay --editmenu --save

To pull and edit the build file:
yay spotify, then select 2 and it will ask you about cleanBuild, diffs and PKGBUILDS to edit use desired options for the first two and then a to edit build file.

Change line 36 from source_x86_64=("${pkgname}-${pkgver}-x86_64.deb::https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_${pkgver}.${_commit}-${_ver_x86_64}_amd64.deb"

to

source_x86_64=("${pkgname}-${pkgver}-x86_64.deb::http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${pkgver}.${_commit}-${_ver_x86_64}_amd64.deb"

Save and exit build file.

Enter y to proceed with install.

I did not have any user issues in Spotify after this. It launched directly to my user home as normal.

Suggestions welcomed from those more knowledgable.
Info pulled from comments at https://aur.archlinux.org/packages/spotify/

1 Like

Hi, yes, I can't install Spotify from aur or even flatpak. I tried your method but it didn't work. :frowning_face:

What errors are you getting?

It seems another common one is:

spotify-1.1.10.546-Release ... FAILED (unknown public key 4773BD5E130D1D45)
==> ERROR: One or more PGP signatures could not be verified!

Directions to fix that error are here:

The $KEYID for this package is 4773BD5E130D1D45

If another issue not related above you can build it manually. In a terminal:
$cd to folder to temporarily store pkg files
$wget https://aur.archlinux.org/cgit/aur.git/snapshot/spotify.tar.gz
$tar -zxvf spotify.tar.gz
$cd spotify
$makepkg -s --skippgpcheck --noconfirm
#pacman -U spotify-1:1.1.10.546-2-x86_64.pkg.tar.xz

Pulled again from comments from aur page linked in Op.

1 Like

I disagree with the suggestion to skip the PGP key check. Instead, you should install the required key with the command

gpg --recv-keys 4773BD5E130D1D45
1 Like

Yes, the (second) problem was the pgp key. I solved it using ben81's solution. Thanks a lot to both of you! :blush::+1::tada:

1 Like

I did leave the info for fixing the key before giving the all-else-fails suggestion. It was just packed with useful info about why rather than the copy-paste solution. :stuck_out_tongue:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by