| 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: | 182 |
| Popularity: | 13.04 |
| First Submitted: | 2023-02-09 22:51 (UTC) |
| Last Updated: | 2024-11-18 16:21 (UTC) |
It was crashing on launch for me with
[0720/122312.041162:FATAL:gpu_data_manager_impl_private.cc(440)] GPU process isn't usable. Goodbye.
140540725722272:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:../../third_party/boringssl/src/ssl/handshake.cc:393:
zsh: trace trap (core dumped) spotify
I had to launch it with this instead
% spotify --no-zygote
removing the whole Spotify folder under /opt directory solved the black screen issue for me after the update
Uh interesting! I also sometimes have it but it is mostly fixed by a restart so far :)
I have to delete my cache to use the new version (UI was black):
rm -rf ~/.cache/spotify
@MarsSeed I personally don't recommend using web.archive.org.
Apart from being considerably slower, I don't think downloading sources anywhere else than the official ones is a good solution. That sounds like a workaround to "patch" the fact that the package isn't actively maintained.
We are working on fixing the latter part instead ;)
@gromit, thank you for the update!
Would you consider my recommendation to use web.archive.org to host the source files? In order to prevent Spotify breaking new installs of this package when they update to a new version and delete the old version.
@angusm please read my earlier comment, I've written a workable solution to that. The current files meant to go into source=() should be saved on web.archive.org, and then the archived copies should be linked to by this AUR package.
Currently prepare() checks that the hash of Packages matches the one mentioned in Release, and that the hash of the deb package itself matches the one mentioned in Packages.
This is reasonable because it establishes a chain of trust from the deb package back to the PGP key that signed Release. It seems the problem is that Packages only contains the hash of the latest version, so this PKGBUILD breaks every time Spotify releases a new version (even if the old version is still available).
Not sure what to do to improve that situation.
Pinned Comments
gromit commented on 2024-01-24 14:22 (UTC) (edited on 2024-02-22 23:00 (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:)