Package Details: spotify 1:1.2.86.502-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: 260
Popularity: 11.88
First Submitted: 2023-02-09 22:51 (UTC)
Last Updated: 2026-04-07 14:56 (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

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

LuffeDeluXe commented on 2026-04-18 14:43 (UTC)

@privatefound thank you so much you're a savior :D

privatefound commented on 2026-04-17 06:30 (UTC) (edited on 2026-04-17 06:31 (UTC) by privatefound)

Temporary fix for audio issue on Spotify package. echo "--audio-api=pulseaudio" >> ~/.config/spotify-flags.conf

LuffeDeluXe commented on 2026-04-14 09:23 (UTC)

After the latest update, I've noticed that spotify no longer controls the application volume, but rather just has what seems like an internal volume setting now. This has significantly limited the range of volume that spotify's own volume slider can control and has made the volume control on my streamdeck less useful, as it utilises spotify's own slider and not application sound. Is this on purpose or because of a bug somewhere? Everything should be up to date on my system

ziris commented on 2026-04-13 02:48 (UTC)

Hopping in here to second @hauke96's experience - spotify suddenly stopped being able to play any song with "Spotify can't play this song right now". Web player worked fine. I added "--audio-api=pulseaudio" to the menu item command and can confirm it's back to working now. I'm not super up-to-speed on audio services, but I see pipewire running in ps, so I thought I was running that, but oh well. Hopefully this flag works for the foreseeable future.

azam commented on 2026-04-13 02:00 (UTC)

@akiirui Thank you! Yeah, that fixes it.

hauke96 commented on 2026-04-12 11:04 (UTC)

With the 1.2.86.502, Spotify stopped playing any songs. The error message "Spotify can't play this song right now. If you have the file on your computer you can import ist" appears whenever I try to play a song.

I don't use pipewire or pipewire-pulse, since it wasn't necessary in the past. I tried deleting the cache via the Spotify UI, deleteing the whole cache folder, deleting the config folder (and logging in again), installing updates, re-installing the package, etc. Nothing helped. The previous version 1.2.84.476 worked just fine, so a downgrade is an easy workaround, but not a permanent solution.

There's another workaround presented in https://community.spotify.com/t5/Desktop-Linux/latest-edge-1-2-86-502-g8cd7fb22-cannot-play-audio-on-Ubuntu-24/m-p/7400080 by specifying the audio API from the CLI with "spotify --audio-api=pulseaudio".

Unfortunately I cannot say where the core problem is. Maybe a missing or outdated dependency? A bug in Spotify itself? Requirement to use pipewire? I don't know. At least there are two workarounds for me, so it's not critical at the moment.

akiirui commented on 2026-04-11 08:12 (UTC)

@azam You can try unset "DISPLAY" environment variable.

Ref: https://github.com/kpcyrd/spotify-launcher/issues/108#issuecomment-4222171171

azam commented on 2026-04-10 17:59 (UTC)

Close button/task tray is resolved on 1:1.2.86.502-1. But now my IME does not work on Spotify. I am using fcitx5 for Wayland for my Japanese input, so probably it will resolve when the app moves back to Wayland? -sigh-

no4b commented on 2026-04-09 21:20 (UTC)

@tpaniaki: Sure, I can easily workaround environment variable issue but I shouldn't have to. I don't have to for earlier versions.

Spotify is the first application that plays sound so no graph is active. It is free to set it to whatever is supported. It should be set to 44.1 kHz in case of Spotify. And exactly this happens when using older Spotify versions. Firefox and mpv doesn't have this problem either. Only latest Spotify (1.2.86.502) does.

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