| 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: | 207 |
| Popularity: | 8.88 |
| First Submitted: | 2023-02-09 22:51 (UTC) |
| Last Updated: | 2025-04-07 11:54 (UTC) |
The latest version of Spotify fails to play local files, even with the optional dependency of ffmpeg4.4 installed.
However, it works with ffmpeg3.4 installed on the system
I can't find anyone else having a similar issue & solution online, so I wanted to bring it up here. I would appreciate it if someone tested & updated the PKGBUILD
The current line Exec=spotify --uri=%u doesn't work properly on my system (Sway, Wayland).
It seems that xdg-utils doesn't support field code placeholders like %u unless they are passed as separate arguments — it ends up calling:
spotify --uri=%u spotify:track:7GhIk7Il098yCjg4BQjzvb
This causes Spotify to ignore the URI entirely.
Interestingly, --uri= appears to be unnecessary. Simply using:
Exec=spotify %u
works fine.
You can test this behaviour directly via:
spotify spotify:track:7GhIk7Il098yCjg4BQjzvb
and then verify the fix with:
xdg-open spotify:track:7GhIk7Il098yCjg4BQjzvb
after modifying the .desktop file.
If you're facing libayatana-appindicator-WARNING **: 00:47:43.531: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code. in Gnome, Install this https://extensions.gnome.org/extension/615/appindicator-support/">Extension
libayatana-appindicator-WARNING **: 00:47:43.531: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.
Clearing ~/.cache/spotify does indeed fix the problem
@Av32000 I had this same behaviour and after deleting ~/.config/spotify and ~/.cache/spotify, it worked again. It may be that only deleting the cache is necessary, which would save you having to log in again.
@Antiz thank you!
Yes it also no longer works for me either as of the last update
plasmashell[1675]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo" : "org.freedesktop.DBus.Error.NotSupported" ""
plasmashell[1675]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo" : "org.freedesktop.DBus.Error.NotSupported" ""
systemd[1263]: Started Spotify - Music Player.
systemd[1263]: app-spotify@9be2d2996be34d2e9c2a3a0cc6735877.service: Main process exited, code=exited, status=1/FAILURE
systemd[1263]: app-spotify@9be2d2996be34d2e9c2a3a0cc6735877.service: Failed with result 'exit-code'.
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?
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:)