Package Details: spotify 1:1.2.59.514-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: Antiz
Votes: 203
Popularity: 11.39
First Submitted: 2023-02-09 22:51 (UTC)
Last Updated: 2025-03-13 07:59 (UTC)

Pinned Comments

gromit commented on 2024-01-24 14:22 (UTC) (edited on 2024-12-28 11:34 (UTC) by gromit)

Please make sure to import the correct GPG key first:

$ curl -sS https://download.spotify.com/debian/pubkey_C85668DF69375001.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, gpg 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 2 3 4 5 6 7 8 9 10 .. 18 Next › Last »

gromit commented on 2024-09-25 15:27 (UTC)

@kokurou should be fixed with the latest versions :) We try to be fast with the updates, but I also don't want to push out untested changes ..

kokurou commented on 2024-09-25 15:06 (UTC)

Hi guys, anyone know how to solve the issue with checksum mismatch for spotify-1.2.45.454-gc16ec9f6-x86_64.deb: FAILED?

match0x0 commented on 2024-09-19 12:35 (UTC)

Thanks for the responses @gromit and @airbreather. airbreather's recommendation did the trick.

not sure why the download was being interrupted. even using curl it failed, but wget worked.

airbreather commented on 2024-09-19 10:51 (UTC)

For whatever reason, the download would tend to get suddenly interrupted when initiated from makepkg. I worked around it by downloading the file with wget (which resumed after the interruption) and then renaming the downloaded file to what the PKGBUILD expected it to be (spotify-1.2.45.454-gc16ec9f6-x86_64.deb)

gromit commented on 2024-09-19 07:32 (UTC)

@auberonlogic works without issue for Antiz and me, which error do you get above?

match0x0 commented on 2024-09-19 02:24 (UTC)

Getting the following error when installing:

"==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.2.45.454.gc16ec9f6_amd64.deb"

Any idea how to resolve?

rob-tech commented on 2024-08-20 18:46 (UTC)

For some reason, the desktop track notifications are not functioning properly. After launching the client, the track notification popup will display for two songs and then each track change after that no longer has any notifications. I'm using KDE Plasma with the latest updates and all Spotify dependencies are fulfilled.

gromit commented on 2024-08-17 17:21 (UTC)

@Baturax thanks, but that'll need fixing by the upstream spotify devlopers :)

Baturax commented on 2024-08-17 16:39 (UTC)

[0817/163855.025507:WARNING:main_runner.cc(261)] Alloy bootstrap is deprecated and will be removed in ~M127. See https://github.com/chromiumembedded/cef/issues/3685

TayntedMemories commented on 2024-08-10 08:14 (UTC) (edited on 2024-08-10 08:21 (UTC) by TayntedMemories)

If you get this error: error: could not extract /opt/spotify/libcef.so (Truncated zstd input) error: problem occurred while installing spotify error: could not commit transaction error: failed to commit transaction (transaction aborted)

It may be because you may have skipped the compression of the package. The step in the makepkg process where it compresses the package, can take a very long time for large packages such as Spotify.

This fix is mainly for the reasons of "chroots take too much disk space." I am personally on a 32GB storage chromebook, and so this is the method I used. This method does eat SOME disk space, but it's a ten-fold decrease (300~MB vs 3~GB) from the space taken up by a chroot. (note, PLEASE use makepkg here, not yay!)

This can be resolved by modifying makepkg.conf, specifically the PKGEXT variable.

Set it to PKGEXT=".pkg.tar" This essentially sets the compression to NONE. Then, run the makepkg as per usual. It should install fine, the only caveat being a large package size.

I do recommend setting it back to the default (.pkg.tar.zst) afterwards, and then, if you use yay normally, then exclude the spotify package from being updated, and every time you need to update the package, do the manual makepkg with the zero compression setting, and set it back when you are done.

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