Package Details: spotify 1:1.2.52.442-1

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: 185
Popularity: 10.41
First Submitted: 2023-02-09 22:51 (UTC)
Last Updated: 2024-12-16 11:48 (UTC)

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:

$ 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.

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 a spotify-flags.conf file under $XDG_CONFIG_HOME or ~/.config :)

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 16 Next › Last »

gromit commented on 2023-09-15 17:10 (UTC) (edited on 2023-09-15 17:10 (UTC) by gromit)

@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 :)

Aerz commented on 2023-09-15 16:57 (UTC)

@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 :)

gromit commented on 2023-09-14 14:21 (UTC)

@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

Aerz commented on 2023-09-14 10:53 (UTC) (edited on 2023-09-15 08:15 (UTC) by Aerz)

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.

lightofpast commented on 2023-09-13 13:26 (UTC) (edited on 2023-09-13 14:01 (UTC) by lightofpast)

Wow, thank you for your great work! @Antiz. However, even though the application reads the flags in the file, it still opens as an x11 window.

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 a spotify-flags.conf file under $XDG_CONFIG_HOME or ~/.config :)

treeshateorcs commented on 2023-09-05 17:04 (UTC)

@lightofpast

edit your spotify desktop file, it should be somewhere in /usr/share/applications, and it has a line that starts with Exec, that's where those arguments should go

lightofpast commented on 2023-08-31 10:32 (UTC) (edited on 2023-08-31 10:41 (UTC) by lightofpast)

Hi all, is there anyway to start the program with "--enable-features=UseOzonePlatform --ozone-platform=wayland" flags automatically? The program seems to run in wayland with these arguments, so is there any configuration files that the application reads before launch (like spotify-flags.conf)?

Antiz commented on 2023-08-20 19:49 (UTC)

@jaytau Just checked the checksums and they're correct. I'm unflagging the package.

phuhl commented on 2023-08-08 12:07 (UTC)

@gromit Ok, sorry, seems to be a false alarm. Apparently, I first started Spotify but the window was somehow not there. The process continued to run though and so starting a new instance did nothing as it immediately quit.

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 16 Next › Last »