| 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: | 220 |
| Popularity: | 11.24 |
| First Submitted: | 2023-02-09 22:51 (UTC) |
| Last Updated: | 2025-05-19 14:19 (UTC) |
Spotify won't launch since the last update (8bfa85f9d3da). When I execute the binary, it stops instantly without any message and with error code 1 (echo $?).
Same problem with the spotify-launcher of pacman
All my packages are up to date and I have Clean Build with yay without error.
Does anyone else have this problem?
I'm getting the error:
could not extract /opt/spotify/libcef.so (Truncated tar archive detected while reading data)
trying to install version 1:1.5.56.502-1 of the package.
Is it just me?
==> Checking for packaging issues... libfakeroot internal error: payload not recognized! ==> Creating package "spotify"...
Anyone else getting this?
@Antiz Thank you very much! :)
@lsigma Thanks for the insight, I updated the parameter from %U to %u ;)
@jkhsjdhjs Fixed (a new version was available, which I just pushed now) ;)
I'm currently seeing the following error:
==> Starting prepare()...
spotify-1.2.53.440-1-x86_64-Packages: OK
spotify-1.2.53.440-g7b2f582a-x86_64.deb: FAILED
sha512sum: WARNING: 1 computed checksum did NOT match
@kotofyt, what error are you getting? Because it works fine for me :)
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:
And always build in a clean chroot. It is as easy as:
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-2that now allows you to set custom launch flags in aspotify-flags.conffile under$XDG_CONFIG_HOMEor~/.config:)