Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Spotify repository linux : missing public Key

Spotify repository linux : missing public Key

Plan

Free

Country

France

 

Device

PC

Operating System

Linux Mint 22.1

 

My Question or Issue

Hello, I've an error when updating software sources in Linux mint 22.1 :
W:GPG error: https://repository.spotify.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C85668DF69375001, E:The repository 'http://repository.spotify.com stable InRelease' is not signed., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., W:https://ppa.launchpadcontent.net/ernstp/mesarc/ubuntu/dists/jammy/InRelease: Signature by key 177961E789BE960FE5E59170B78C97EF9B2235DD uses weak algorithm (rsa1024), W:https://ppa.launchpadcontent.net/vincent-vandevyvre/vvv/ubuntu/dists/jammy/InRelease: Signature by key 7CAA00CD3DCA73E24812D646A5ADEEFF89F92A1A uses weak algorithm (rsa1024)

 

I tried to add the public key with command :

sudo curl -sS https://download.spotify.com/debian/pubkey_C85668DF69375001.gpg | sudo gpg --dearmor --yes -o /etc/apt/trusted.gpg.d/spotify.gpg

 

But it didn't change anything, I always have this error.

 

Reply
5 Replies

It looks like your Spotify repository public key is missing or outdated. Since Ubuntu-based distributions (like Linux Mint) now use a different key management system, you’ll need to add the correct GPG key using a different method. Here’s how to fix it:

  1. Remove the old Spotify GPG key (if it exists):

    bash
     
    sudo rm -f /etc/apt/trusted.gpg.d/spotify.gpg
  2. Add the new public key the correct way:

    bash
     
    sudo mkdir -p /etc/apt/keyrings curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | sudo tee /etc/apt/keyrings/spotify.gpg > /dev/null
  3. Update your repository entry to use the new key location:

    bash
     
    echo "deb [signed-by=/etc/apt/keyrings/spotify.gpg] http://repository.spotify.com stable non-free" | sudo tee /etc/apt/sources.list.d/spotify.list
  4. Update the package list and install Spotify:

    bash
     
    sudo apt update && sudo apt install spotify-client

 

Let me know if you need more help! 😊

ribezazSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

Hello,

thank you very much for your support.

I did all commands and checked the directories and files. But, when all was done "apt update" send me the same error :

W: Erreur de GPG : https://repository.spotify.com stable InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY C85668DF69375001
E: Le dépôt http://repository.spotify.com stable InRelease n'est pas signé.

 

Sorry it's in french language, my system is n french.

It seems the signature cannot be checked because the system doesn't recognize the public key to check. And it said that the repository is not signed.

I don't understand.

 

I think I'll use a workaround by installing the flatpak from flathub. (system package is version 1.2.37, flatpak is in version 1.2.52). I must also remove the spotify repository from my software sources, if not i've always an error when updating the cache and it is a problem when upgrading Mint.

@Gebe_76 

 

Hello again!

 

I did some research on your issue, and I just found out that Linux devices are not officially supported, and that might be the reason why you are getting these errors.

 

Cheers,
ribezaz

ribezazSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

Thank you Ribezaz

Yes I think it is the problem. So the best is to use the flatpak in place of system repository, or simply use the web interface with any browser.

So still thanks for your help.
Friendly.

Gebe

You're welcome! If you need help, look for the Community, we'll always be willing to help you!

ribezazSpotify Star
Help others find this answer and click "Accept as Solution".
If you appreciate my answer, maybe give me a Like.
Note: I'm not a Spotify employee.

Suggested posts