Arch Linux User Repository

Please make sure to import the correct GPG key first:

$ curl -sS https://download.spotify.com/debian/pubkey_6224F9941A8AA6D1.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.

@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 :)

Hi all. I've been having issues with downloading the .deb for this package for a while now. Same issue I've seen mentioned here before. I've been working around it by manually downloading the .deb file. I got tired of doing that every upgrade so I added some download retry logic to the PKGBUILD to do it automatically. Modified PKGBUILD here: https://pastebin.com/ek1ehpQW

With that PKGBUILD it will retry 3 times, resuming where it left off:

❯ makepkg
==> Making package: spotify 1:1.2.50.335-1 (Thu 21 Nov 2024 02:54:16 PM MST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
  -> Downloading Spotify .deb package...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  1  136M    1 1654k    0     0   313k      0  0:07:28  0:00:05  0:07:23  379k
curl: (18) end of response with 141922858 bytes missing
Download failed, retrying in 3 seconds...
Attempt 2 of 3: Resuming download...
** Resuming transfer from byte position 1694290
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 82  135M   82  111M    0     0  21.3M      0  0:00:06  0:00:05  0:00:01 27.0M
curl: (18) end of response with 24767680 bytes missing
Download failed, retrying in 3 seconds...
Attempt 3 of 3: Resuming download...
** Resuming transfer from byte position 118849468
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 23.6M  100 23.6M    0     0  34.4M      0 --:--:-- --:--:-- --:--:-- 34.4M
  -> Downloading Release file...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2447  100  2447    0     0   6177      0 --:--:-- --:--:-- --:--:--  6179
  -> Downloading Release signature...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   833  100   833    0     0   2119      0 --:--:-- --:--:-- --:--:--  2125
  -> Downloading Packages file...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1132  100  1132    0     0   3190      0 --:--:-- --:--:-- --:--:--  3188
==> Validating source files with sha512sums...
    spotify-1.2.50.335-g5e2860a8-x86_64.deb ... Passed
    spotify.sh ... Passed
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.2.50.335-1-Release ... Skipped
    spotify-1.2.50.335-1-Release.sig ... Skipped
    spotify-1.2.50.335-1-x86_64-Packages ... Skipped
==> Verifying source file signatures with gpg...
    spotify-1.2.50.335-1-Release ... Passed
==> Extracting sources...
  -> Extracting spotify-1.2.50.335-g5e2860a8-x86_64.deb with bsdtar
==> Starting prepare()...
  -> Spotify .deb package already exists, skipping download
  -> Release file already exists, skipping download
  -> Release signature already exists, skipping download
  -> Packages file already exists, skipping download
spotify-1.2.50.335-1-x86_64-Packages: OK
spotify-1.2.50.335-g5e2860a8-x86_64.deb: OK
==> Entering fakeroot environment...
...

@gromit feel free to add this to the official PKGBUILD :)

@gromit Okay thanks

@EfremchickEga of course this package works, I use it every day. The installation requirements are documented in the PKGBUILD so if you have any trouble installing that please voice a more specific question!

Hello, can you please tell me if this package works now and what is needed to install this package?

@martian0x80 I just re-verified that the checksums match. Which source fails for you?

Kept getting a seg fault on 1.2.48.405-1,

[1] 120448 segmentation fault (core dumped) spotify

so tried to upgrade to 1.2.50.335-1, then got checksum mismatch,

sha512sum: WARNING: 1 computed checksum did NOT match

so,

yay -S --mflags --skipinteg spotify

installed, but still get a seg fault, launching through gdb freezes the spotify window at the initial black screen.

Help?

Seems like the issue with the explicit_filter.restore file is fixed in today's version (1.2.48.405).

https://community.spotify.com/t5/Desktop-Linux/Weird-file-appearing-on-linux-in-home-directory/td-p/6399472

Seems like the explicit_filter.restore problem can be mitigated by switching spotify's work path to /tmp so that the file is created in /tmp instead of the user directory

Hi,

I did the changes %U to %u (don't really know if it was an answear to my problem or someone elses) but result is still the same...

Still stuck with [f:248 ] Ending step: cef_context_init Instruction not allowed (core dumped)

Thanks for your help

Hi, not sure if you're able to do anything about this, but recently Spotify started putting an empty file "explicit_filter.restore" to $HOME. I found it happens when you play and pause the player or kill the app. Not on launch.