Arch Linux User Repository

Please make sure to import the correct GPG key first:

$ curl -sS https://download.spotify.com/debian/pubkey_6224F9941A8AA6D1.gpg  | gpg --import -

And always build in a clean chroot. It is as easy as:

pacman -S devtools
git clone https://aur.archlinux.org/spotify.git
cd spotify
pkgctl build
pacman -U <path-to-spotify-package>

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.

@lightofpast Just pushed v1:1.2.20.1210-2 that now allows you to set custom launch flags in a spotify-flags.conf file under $XDG_CONFIG_HOME or ~/.config :)

@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

@Aerz Actually both things are expected:

• Separate flags belong on different lines
• The full line (if its not a comment) is passed to spotify as arg

You are actually causing the oddy behaviour by having a space at the end of the line in the config:

# With space
+ exec /opt/spotify/spotify '--enable-features=UseOzonePlatform ' --ozone-platform=wayland

# Without space
+ exec /opt/spotify/spotify --enable-features=UseOzonePlatform --ozone-platform=wayland

So I think it is fine as is but I am open to suggestions as I personally dont need to pass any flags to spotify :)

@grommit Thanks for doing an update. I've been tested but it still doesn't work at all.

In case all arguments goes to the first line in the config file:

# ~/.config/spotify-flags.conf
--enable-features=UseOzonePlatform --ozone-platform=wayland

I still see one string when I set set -x in the script wrapper:

+ exec /opt/spotify/spotify '--enable-features=UseOzonePlatform  --ozone-platform=wayland'

And setting one argument per line in config, it works but getting an oddy result:

+ exec /opt/spotify/spotify '--enable-features=UseOzonePlatform ' --ozone-platform=wayland

If you liked the previous solution, you could remove the quotes when using the SPOTIFY_USER_FLAGS just as google-chrome package does. You will see the SC2086 warning but I think is fine :)

@Aerz I have pushed a different version of the script that contains your suggestions in a modified way. Let me know if that still does not work out for you!

Background info: We took the launch scripts from the google-chrome package as base for these ones but now the vars are quoted where they previously werent.. So the difference was really subtle :p

Hi. I've been trying out the new spotify-flags.conf and I've noticed that the flags are not being captured properly. . The script sends all the flags as a single string.

exec /opt/spotify/spotify '--enable-features=UseOzonePlatform --ozone-platform=wayland'

A really quick fix might be to remove the quotes from "${SPOTIFY_USER_FLAGS}"but another way I suggest is to use mapfile to convert the config file to an array to use each argument in a clean way. The bad thing is one argument per line.

#!/usr/bin/env bash

# Substitute XDG_CONFIG_HOME by ~/.config if the env var is unset or empty
XDG_CONFIG_HOME=${XDG_CONFIG_HOME:-~/.config}

# Allow users to override command-line options
if [[ -f "${XDG_CONFIG_HOME}/spotify-flags.conf" ]]; then
    mapfile -t SPOTIFY_USER_FLAGS < "${XDG_CONFIG_HOME}/spotify-flags.conf"
    echo "User flags:" "${SPOTIFY_USER_FLAGS[@]}"
fi

# Launch Spotify
exec /opt/spotify/spotify "${SPOTIFY_USER_FLAGS[@]}" "${@}"

Feel free to use it and thank you for your work.