Package Details: spotify 1:1.2.89.539-1

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: gromit
Votes: 266
Popularity: 12.14
First Submitted: 2023-02-09 22:51 (UTC)
Last Updated: 2026-05-18 14:53 (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 <path-to-spotify-package>

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

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 27 Next › Last »

Yuuupie commented on 2023-12-14 09:59 (UTC)

@bosma @me44ic05 Was getting the same error with download failing midway. Out of desperation I re-imported the GPG key despite already having it "curl -sS https://download.spotify.com/debian/pubkey_7A3A762FAFD4A51F.gpg | gpg --import -a" and it started working again. Might help.

diogobaeder commented on 2023-12-08 03:12 (UTC)

I'm not sure what went on with the latest changes for the Spotify client or GNOME, but, if you leave the "minimize on close" option on, lock your screen, and unlock it back, Spotify breaks the interactions with the windows (close, select tab etc). I'm trying to understand the extent of the error before I file a more detailed bug report.

me44ic05 commented on 2023-11-24 06:39 (UTC)

@bosma I've been getting the same. The main package download will fail with some arbitrary number of bytes remaining. I've had to clone this repo and manually run makepkg -i multiple times every time there's an update to get it to push through to a fully complete download.

I think it may be isolated to some networks: jumping on a VM on a cloud provider seemed to present no issue with downloading the package. I haven't looked much further though.

Antiz commented on 2023-11-22 12:32 (UTC)

@sterni1971 A new version came out in the meantime (v1.2.25.1011) causing the upgrade to v1.2.25.1009 to fail. I just updated the package ;)

sterni1971 commented on 2023-11-22 12:24 (UTC)

Update failed with

==> Starting prepare()... spotify-1.2.25.1009-1-x86_64-Packages: OK spotify-1.2.25.1009-g075ce884-x86_64.deb: FAILED sha512sum: WARNING: 1 computed checksum did NOT match ==> ERROR: A failure occurred in prepare(). Aborting... -> error making: spotify-exit status 4 -> Failed to install the following packages. Manual intervention is required: spotify - exit status 4

pienapin commented on 2023-11-17 01:11 (UTC) (edited on 2023-11-17 01:12 (UTC) by pienapin)

I also had the same problem with blank screen. Solved by executing my WM (BSPWM) with "dbus-run-session bspwm"

acd commented on 2023-11-06 18:16 (UTC)

I just had the same problem with a blank screen on start. Solved it by disabling KeepassXC's Secret Service Integration.

marvhus commented on 2023-10-24 15:52 (UTC) (edited on 2023-11-25 01:16 (UTC) by marvhus)

@lrmb I'm having the same issue.
Also, when I start spotify I can't close it, and it's using a lot of CPU.
(Using pkill, kill, killall didn't work, I had to send it SIGSEGV to make it stop)

I am on X11 btw.
I have tried opening it on KDE (X11) and DWM, and it happens on both.

EDIT: It turns out it didn't work because DBUS_SESSION_BUS_ADDRESS was set to /dev/null Setting it to something like: unix:path=/run/user/1000/bus Fixed it in my case. I did this by placing these two lines in my startx script: export XDG_RUNTIME_DIR="/run/user/$UID" export DBUS_SESSION_BUS_ADDRESS="unix:path=${XDG_RUNTIME_DIR}/bus"

gromit commented on 2023-10-21 22:42 (UTC)

@lrmb, no I use it daily, there most likely is some kind of error on your side ... Are you using wayland perhaps?

Also you could try to start spotify from the cli to see if there is any useful output there :)

lrmb commented on 2023-10-21 18:30 (UTC)

Running spotify from this package shows an empty window and then nothing happens, no welcome or login screen. I wonder if it might have something to do with the latest change about setting custom flags.

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 27 Next › Last »