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 2 3 4 5 6 7 .. 17 Next › Last »

gromit commented on 2024-11-18 17:23 (UTC)

@martian0x80 I just re-verified that the checksums match. Which source fails for you?

martian0x80 commented on 2024-11-18 16:46 (UTC)

Kept getting a seg fault on 1.2.48.405-1,

[1] 120448 segmentation fault (core dumped) spotify

so tried to upgrade to 1.2.50.335-1, then got checksum mismatch,

sha512sum: WARNING: 1 computed checksum did NOT match

so,

yay -S --mflags --skipinteg spotify

installed, but still get a seg fault, launching through gdb freezes the spotify window at the initial black screen.

Help?

birdip commented on 2024-10-21 15:55 (UTC)

Seems like the issue with the explicit_filter.restore file is fixed in today's version (1.2.48.405).

kaneki commented on 2024-10-13 19:41 (UTC)

https://community.spotify.com/t5/Desktop-Linux/Weird-file-appearing-on-linux-in-home-directory/td-p/6399472

Seems like the explicit_filter.restore problem can be mitigated by switching spotify's work path to /tmp so that the file is created in /tmp instead of the user directory

Apolo-XIII commented on 2024-10-10 08:26 (UTC)

Hi,

I did the changes %U to %u (don't really know if it was an answear to my problem or someone elses) but result is still the same...

Still stuck with [f:248 ] Ending step: cef_context_init Instruction not allowed (core dumped)

Thanks for your help

ronneycz commented on 2024-10-05 12:19 (UTC)

Hi, not sure if you're able to do anything about this, but recently Spotify started putting an empty file "explicit_filter.restore" to $HOME. I found it happens when you play and pause the player or kill the app. Not on launch.

jlindgren commented on 2024-10-05 09:44 (UTC)

Hi, there is a small typo in the "sed" line that modifies the .desktop file. The "--uri=%U" should be "--uri=%u" (lowercase 'u') instead because only a single URI argument works there. It's causing labwc-git to fail to parse the .desktop file, and as a result Spotify gets no icon.

Apolo-XIII commented on 2024-10-03 08:30 (UTC) (edited on 2024-10-03 08:34 (UTC) by Apolo-XIII)

Hi, spotify used to work fine, but I have some troubles now. I tried to make a reinstall of the package but problem is still here.

Hope you can help. Thanks

Hereafter the most detailed log from app: spotify --show-console --debug-level=MAX

08:25:43.178 E [f:25 ] TCPServer: Failed to create port checker

08:25:43.191 I [f:229 ] Starting step: core_init

08:25:43.191 I [f:159 ] Access allowance changed from online: 0 stream: 0, sync: 0, persistent conn: 0 to online: 1 stream: 1, sync: 0, persistent conn: 1

08:25:43.192 E [f:44 ] Unable to open settings file for reading: /home/polo/.cache/spotify/hosts.bnk

08:25:43.192 I [f:77 ] Connectivity policy is initially allow_all

08:25:43.192 I [f:79 ] Connection type is initially unknown

08:25:43.192 I [f:96 ] Enabling all persistent connections

08:25:43.192 I [f:139 ] Open storage index header at /home/polo/.cache/spotify/Storage/index.dat

08:25:43.192 I [f:30 ] Created or reset storage index at /home/polo/.cache/spotify/Storage (this most likely means new install)

08:25:43.192 I [f:271 ] NmNetworkNotifier is not aware of running NetworkManager (yet), assume 'ethernet'

08:25:43.192 I [f:248 ] Ending step: core_init

08:25:43.192 E [f:1405 ] Failed to set default autostart mode!

08:25:43.226 I [f:229 ] Starting step: cef_context_init

08:25:43.230 I [f:134 ] D-Bus name 'org.freedesktop.NetworkManager' exists on the system bus

08:25:43.232 I [f:139 ] Notify subscribers on NetworkManager detection (current state is 'NM_STATE_CONNECTED_GLOBAL')

08:25:43.232 I [f:190 ] Successfully connected to 'org.freedesktop.NetworkManager'

08:25:43.244 I [f:229 ] Starting step: main_view_init

08:25:43.247 I [f:248 ] Ending step: cef_context_init Instruction non permise (core dumped)

quebn commented on 2024-09-28 13:56 (UTC) (edited on 2024-09-28 13:57 (UTC) by quebn)

I am using the pacman package and ~/explicit_filter.restore also created every time a song is played/unpaused, might have something to do with the latest Spotify update.

LRitzdorf commented on 2024-09-28 05:02 (UTC)

The same ~/explicit_filter.restore file appears for me, as soon as a play (including "un-pausing") seemingly any song.

@Muksiz No spicetify here; I'm using just classic Spotify via this package.

« First ‹ Previous 1 2 3 4 5 6 7 .. 17 Next › Last »