@gromit Interesting, no for me that is all the output, then nothing happens. Any other output I can provide?
EDIT: nothing happens = spotify executable quits, no window was ever opened
| 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: | 266 |
| Popularity: | 11.90 |
| First Submitted: | 2023-02-09 22:51 (UTC) |
| Last Updated: | 2026-05-18 14:53 (UTC) |
« First ‹ Previous 1 .. 16 17 18 19 20 21 22 23 24 25 26 27 Next › Last »
@gromit Interesting, no for me that is all the output, then nothing happens. Any other output I can provide?
EDIT: nothing happens = spotify executable quits, no window was ever opened
@phuhl, works fine for me although there seems to be some cli output:
spotify 134 ↵
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
But afterwards spotify starts and works fine ... Do you get more output?
Seems there is a new version of libcurl-gnutls that is not compatible and prevents spotify from starting:
$ spotify
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
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.
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:
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, 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-2that now allows you to set custom launch flags in aspotify-flags.conffile under$XDG_CONFIG_HOMEor~/.config:)