Package Details: spotify 1:1.2.96.518-2

Git Clone URL: https://aur.archlinux.org/spotify.git (read-only, click to copy)
Package Base: spotify
Description: A proprietary music streaming service
Upstream URL: https://www.spotify.com
Licenses: custom
Submitter: Foxboron
Maintainer: gromit (Antiz)
Last Packager: Antiz
Votes: 276
Popularity: 6.22
First Submitted: 2023-02-09 22:51 (UTC)
Last Updated: 2026-08-26 17:40 (UTC)

Pinned Comments

Antiz commented on 2025-11-23 18:37 (UTC) (edited on 2025-11-23 18:41 (UTC) by Antiz)

Please make sure to import the correct OpenPGP key first:

$ curl -sS https://download.spotify.com/debian/pubkey_5384CE82BA52C83A.gpg | gpg --import -

And always build in a clean chroot. It is as easy as:

pacman -S devtools
git clone https://aur.archlinux.org/spotify.git
cd spotify
pkgctl build
pacman -U

It is expected that the package will break now and then, as spotify continuously changes download binaries, OpenPGP keys, etc (which is not appropriate, but we cannot change this). Please be patient if an update does not occur the next day, you can still use an existing spotify install or update the version yourself.

Antiz commented on 2023-09-13 13:21 (UTC)

@lightofpast Just pushed v1:1.2.20.1210-2 that now allows you to set custom launch flags in a spotify-flags.conf file under $XDG_CONFIG_HOME or ~/.config :)

Latest Comments

1 2 3 4 5 6 .. 28 Next › Last »

inky commented on 2026-08-29 12:28 (UTC)

couldn't autobuild 1.2.96.518-2 with paru. cloned, tried it manually in clean chroot - the error is that I can't download the .sig file

Had to change all http:// schema to https:// in .SRCINFO and PKGBUILD - clean chroot build succeeds, the package can be built.

Antiz commented on 2026-08-26 17:40 (UTC)

@ggdG @agarof, this should be fixed now. Thanks for the heads up :)

agarof commented on 2026-08-26 16:38 (UTC)

To add to the previous comment, spotify needs both libayatana-appindicator and libayatana-indicator. libayatana-appindicator's dependency on libayatana-indicator was recently removed in this commit.

ggdG commented on 2026-08-26 13:06 (UTC) (edited on 2026-08-26 13:08 (UTC) by ggdG)

Spotify cannot start correctly.

spotify[18277]: /opt/spotify/spotify: error while loading shared libraries: libayatana-indicator3.so.7: cannot open shared object file: No such file or directory

libayatana-appindicator doesn't have libayatana-indicator3.so.7. While libayatana-indicator has.

naxels commented on 2026-08-17 13:03 (UTC) (edited on 2026-08-17 13:08 (UTC) by naxels)

Unfortunately the source= "${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages" is broken for 1.2.95..

https://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages

returns a newer version: Version: 1:1.2.96.518.g366879e1

and therefor upon install i receive this error:

==> Extracting sources...
  -> Extracting spotify-1.2.95.453-g0eeebbed-x86_64.deb with bsdtar
==> Starting prepare()...
spotify-1.2.95.453-1-x86_64-Packages: OK
spotify-1.2.95.453-g0eeebbed-x86_64.deb: FAILED
sha512sum: WARNING: 1 computed checksum did NOT match
==> ERROR: A failure occurred in prepare().
    Aborting...
Failed to build package

Also it seems that starting today the listing on https://repository-origin.spotify.com/pool/non-free/s/spotify-client/

also has the newer spotify-client_1.2.96.518.g366879e1_amd64.deb listed

pika commented on 2026-08-10 01:57 (UTC) (edited on 2026-08-10 01:58 (UTC) by pika)

Looks like the underlying Packages file changed -- the following patch builds for me (making the PKGBUILD reflect the actual Packages file):

diff --git a/PKGBUILD b/PKGBUILD
index 4333fe7..7c2cc03 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -6,9 +6,9 @@
 # Contributor: Eothred 

 pkgname=spotify
-pkgver='1.2.92.147'
+pkgver='1.2.95.453'
 epoch=1
-_commit=g5b8f9367
+_commit=g0eeebbed
 pkgrel=1
 pkgdesc='A proprietary music streaming service'
 arch=('x86_64')
@@ -34,7 +34,7 @@ source=("${pkgname}-${pkgver}-${_commit}-x86_64.deb::http://repository.spotify.c
         "${pkgname}-${pkgver}-${pkgrel}-Release::http://repository.spotify.com/dists/testing/Release"
         "${pkgname}-${pkgver}-${pkgrel}-Release.sig::http://repository.spotify.com/dists/testing/Release.gpg"
         "${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages")
-sha512sums=('e84afeaa3c011c7e06cffa31d0a0113f8851bad57fc26317c2eef74b89985848bdd25b72e4f9a9e55948b8b927f3205a8b9c1047e2f28eec500ac7a2d4913cad'
+sha512sums=('902d9b8200d67e10a19ce5e34316ea14ed05e935fe5493c21f7a8db31b2ffc91375dd18a68734e781b815d57ac9e3aff36da79bce9ff6882a1f247542caab451'
             'da48b628a4ea925dd8521133ebf364b261b11aed252d264dde6605d915cdb631919ffe672c58534bcdb60869e5d87a49a60a8198780b99517123f0031e83fdb1'
             '999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'

avenita commented on 2026-08-08 20:48 (UTC)

we have a checksum fail yet again.

larsrh commented on 2026-07-25 12:15 (UTC) (edited on 2026-07-25 12:16 (UTC) by larsrh)

The following worked for me:

$ cat .config/spotify-flags.conf
--audio-api=pulseaudio

dboneham commented on 2026-07-10 11:55 (UTC)

Per almond.flour4's comment, I got rid of the error by using an alias for "spotify", this being "spotify --audio-api=pulseaudio". I think you could alternatively do this by including the above in spotify webplayer flags as an environment setting in your .bashrc/.zshrc or .profile file.

almond.flour4 commented on 2026-05-29 03:06 (UTC) (edited on 2026-05-29 03:06 (UTC) by almond.flour4)

For the current version of the Spotify package with the "Cannot Play Current Song" error, it looks like it's from a pipewire permissions error. See https://community.spotify.com/t5/Desktop-Linux/latest-edge-1-2-86-502-g8cd7fb22-cannot-play-audio-on-Ubuntu-24/td-p/7400080

You can either manually link pipewire permissions via snap connect spotify:pipewire or just run spotify with an alternate audio api flag that you have installed (such as spotify --audio-api=pulseaudio)

1 2 3 4 5 6 .. 28 Next › Last »