Package Details: spotify 1:1.1.10.546-1

Git Clone URL: https://aur.archlinux.org/spotify.git (read-only)
Package Base: spotify
Description: A proprietary music streaming service
Upstream URL: https://www.spotify.com
Licenses: custom
Submitter: gadget3000
Maintainer: AWhetter (NicoHood)
Last Packager: AWhetter
Votes: 1836
Popularity: 39.612936
First Submitted: 2010-07-12 12:17
Last Updated: 2019-08-30 05:47

Pinned Comments

carloshmm commented on 2019-08-29 02:51

@NicoHood

They just added this as a official idea! https://community.spotify.com/t5/Live-Ideas/Linux-Add-Spotify-to-the-official-Linux-repositories/idi-p/4813156

Please help spread the word!

NicoHood commented on 2017-05-28 14:45

@Lenovsky There you go. Please upvote this topic if you wish to have spotify in the official ArchLinux [community] repository.

https://community.spotify.com/t5/Desktop-Linux-Windows-Web-Player/Redistribute-Spotify-on-Linux-Distributions/m-p/1695334#M188735

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

un_deaddy commented on 2019-08-07 15:38

I also have a problem with installing version 1.1.10

    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.10.546-Release ... FAILED
    spotify-1.1.10.546-Release.sig ... Skipped
==> ERROR: One or more files did not pass the validity check!

Importing keys didn't work.

8sd commented on 2019-08-07 12:32

When installing the current version 1.1.10 I get the following error:

    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.10.546-Release ... FAILED
    spotify-1.1.10.546-Release.sig ... Skipped
==> ERROR: One or more files did not pass the validity check!

cbartsch commented on 2019-08-05 19:24

@orangecake I have the same issue on 1.0.94.262

orangecake commented on 2019-08-02 17:31

@reikdas I am still on 1.1.5.153 and your observation makes me hesitant to actually upgrade. Did you also get this issue with 1.1.5.153 or did it just occur with 1.1.10.546?

reikdas commented on 2019-07-30 14:43

My liked songs list doesn't sync with my account for some reason.

rbellamy commented on 2019-07-29 20:21

None of the typical solutions worked for me, including using a specific keyserver.

What worked for me is to temporarily disable setting SHA1 as a weak digest in the global gpg config by commenting the line like so:

#weak-digest SHA1

Dante_Igashu commented on 2019-07-25 21:59

@matrs Hello!!! I used to have a similar problem before with the spotify's key and, if I recall correclty, the "ffmpeg2.8" key. Then I found a comment from a person called "sciant" somewhere between all the coments here and since I started using that person's method I had had no problem adding those two keys. Just add it this way and it may allow you to update spotify:

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys A87FF9DF48BF1C90

Good Luck!! :D

matrs commented on 2019-07-25 17:34

When I do $ gpg --recv-key A87FF9DF48BF1C90 I get:

gpg: key A87FF9DF48BF1C90: 1 signature not checked due to a missing key
gpg: key A87FF9DF48BF1C90: public key "Spotify Public Repository Signing Key <tux@spotify.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1

and then When i try to update spotify I still get: One or more PGP signatures could not be verified!

Any suggestions?

polylux commented on 2019-07-24 11:35

You need to also import the spotify key to the keyring of your normal user as keycheck is performed with it using pacaur, yaourt, ... Hence do a

gpg --recv-key A87FF9DF48BF1C90

and you're good to go.

yuu commented on 2019-07-20 22:32

How to change playback device? help me. I found for windows but no for linux.