@lrmb, no I use it daily, there most likely is some kind of error on your side ... Are you using wayland perhaps?
Also you could try to start spotify from the cli to see if there is any useful output there :)
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: | Antiz |
Votes: | 209 |
Popularity: | 12.88 |
First Submitted: | 2023-02-09 22:51 (UTC) |
Last Updated: | 2025-03-13 07:59 (UTC) |
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 18 Next › Last »
@lrmb, no I use it daily, there most likely is some kind of error on your side ... Are you using wayland perhaps?
Also you could try to start spotify from the cli to see if there is any useful output there :)
Running spotify
from this package shows an empty window and then nothing happens, no welcome or login screen.
I wonder if it might have something to do with the latest change about setting custom flags.
curl: (18) transfer closed with 7733012 bytes remaining to read
==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.2.22.982.g794acc0a_amd64.deb
Aborting...
:: Unable to build spotify - makepkg exited with code: 1
I've been occasionally getting this error just from this package, some updates have gone through (it's not consistent).
Spotify seems to have a tray icon now but presumably the icon is not installed since I can only see the space where it's supposed to be in my tray.
Can this be fixed please?
If spotify is minimized to tray, you can't un-minimize it from tray.
If you launch spotify again in this state, playback will stop.
This is because spotify is launched with option --uri=
by .desktop file.
So, I modified .desktop file with just %U
instead of --uri=%U
, and /usr/bin/spotify
as follows:
commline="$@"
[[ ${#commline} > 0 && "${commline:0:2}" != "--" ]] && commline="--uri=$commline"
# Launch Spotify with the given flags
exec /opt/spotify/spotify "${SPOTIFY_USER_FLAGS[@]}" "$commline"
@gromit yup i did, ended up using debtap to install the app from a debian binary
I'm getting a grey screen with nothing loading with the newest version of both this pkg and the spotify-launcher
pkg. Not sure what both have in common, but I've pasted relevant info in an issue on the spotify-launcher
's github, since that's where I experienced it first (and the output to the terminal is the exact same). As stated in the github issue, I am able to use an older version of this pkg without issue in the meantime.
I'm guessing I'm just missing something obvious, or maybe I have a dependency issue, not sure.
EDIT: it was not something obvious, but I did finally figure it out, nothing to do with spotify, even if spotify was the only thing affected on my system. For a full write-up and resolution, check out the aforementioned issue I opened on the spotify-launcher github.
TLDR: code green, false alarm.
my Song Changes Notifications only show for the first 1-2 songs I played, and I have to click Close Button on Notification to keep it coming.
my System: KDE with X11, 6.5.5-AMD-znver2 Kernel
@phoenix277yt did you try to also build as the pinned comment advises (with devtools
in a clean chroot)? Most likely this is an error with your AUR helper.
Generally the package builds just fine for me and the type of error suggests that you are only missing the gpg key and not that this would need changes from the packaging side.
Spotify breaks when installing for me, something to do with gpg keys.
when running
curl -sS https://download.spotify.com/debian/pubkey_7A3A762FAFD4A51F.gpg | gpg --import -
i get
gpg: Total number processed: 1
gpg: unchanged: 1
and when building with yay, i get
==> Verifying source file signatures with gpg...
spotify-1.2.20.1210-3-Release ... FAILED (unknown public key 7A3A762FAFD4A51F)
==> ERROR: One or more PGP signatures could not be verified!
-> error making: spotify-exit status 1
-> Failed to install the following packages. Manual intervention is required:
spotify - exit status 1
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-2
that now allows you to set custom launch flags in aspotify-flags.conf
file under$XDG_CONFIG_HOME
or~/.config
:)