Repository 'http://repository.spotify.com stable InRelease' is not signed

Solved!
Reply

Repository 'http://repository.spotify.com stable InRelease' is not signed

astr011
Casual Listener

Operating System

Debian testing

 

My Question or Issue

 W: GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EFDC8610341D9410
E: The repository 'http://repository.spotify.com stable InRelease' is not signed.

1 ACCEPTED SOLUTION

Accepted Solutions
Solution!

Re: Repository 'http://repository.spotify.com stable InRelease' is not signed

astr011
Casual Listener

Indeed, they fixed it. But they didn't even care to come here and tell us it was fixed. Thanks for the support, Spotify! All good, people.

View solution in original post

12 Replies

Re: Repository 'http://repository.spotify.com stable InRelease' is not signed

Zocker1999NET
Newbie

Same issue here.

The repository is signed with a key different from the key given at https://www.spotify.com/de/download/linux/

Key used to sign the repository: EFDC8610341D9410

Spotify, please confirm new key or sign the repository with the old key.

Highlighted

Re: Repository 'http://repository.spotify.com stable InRelease' is not signed

hemulin1
Newbie

Same here
(Lubuntu 16.04, spotify-client 1:1.0.80.480.g51b03ac3-13)

 

W: An error occurred during the signature verification.
The repository is not updated and the previous index files will be used.
GPG error: http://repository.spotify.com stable InRelease:
The following signatures were invalid: KEYEXPIRED 1532522191

Re: Repository 'http://repository.spotify.com stable InRelease' is not signed

IronWolve
Regular

Having the same issue on both stable and testing, pgp key is wrong.

Re: Repository 'http://repository.spotify.com stable InRelease' is not signed

jdferron
Newbie

Also having the same issue.  Please fix!

Re: Repository 'http://repository.spotify.com stable InRelease' is not signed

nmax
Newbie

Same.  I think this is a repeated error.

 

Ubuntu 18.04, sudo apt update:

 

"The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EFDC8610341D9410"GPG error: http://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EFDC8610341D9410
W: Failed to fetch http://repository.spotify.com/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EFDC8610341D9410"

 

 

(No Subject)

astr011
Casual Listener
As far as I can tell Spotify has been hacked and someone is messing up with the repository. It wouldn't surprise me if someone had embedded a cryptocurrency miner in the software. I'm loving how Spotify has been super fast to solve this, lol.

Re: Repository 'http://repository.spotify.com stable InRelease' is not signed

jsone
Casual Listener

same problem here on ubuntu 16.04.

Re: Repository 'http://repository.spotify.com stable InRelease' is not signed

soundblaster16
Casual Listener

Since yesterday I got a similar/the same issue on Linux Mint 18.3 x64 when updating apt:

GPG error: http://repository.spotify.com stable InRelease

The reason phrase states "KEYEXPIRED"

 

Tried to update the key which didn't change anything:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

Re: Repository 'http://repository.spotify.com stable InRelease' is not signed

ffissore
Regular

Same here

SUGGESTED POSTS