Announcements

Help Wizard

Step 1

NEXT STEP

Recent Linux client update changes (2026)

Recent Linux client update changes (2026)

Hey folks! 

 

This is a heads-up that there will be a new update to the Spotify Linux client signatures. The latest available client will not install this new key just yet, but it's coming soon.

Come February, you may see errors related to missing keys and failed signatures when trying to update Spotify if you haven't installed the new key. Note that it will be installed automatically starting with the upcoming client update.

 

Here is the updated key:

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


For further instructions on how to install Spotify on Linux, check out this support page here.

Have a nice day!

VasilModerator
Help others find this answer and click "Accept as Solution".
If you appreciate an answer, maybe give it a Like.
Are you new to the Community? Take a moment to introduce yourself!
Reply
26 Replies

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

I cannot possibly run this command on all the machines that I manage out there with Spotify installed on it, I manage systems Linux Mint Cinnamon and running a simple sudo apt update reveals that the public key is still incorrect at the moment.

 

Will it be updated automatically at some point and how will I be able know?

And, am I right to notice that other automatic system updates in Linux Mint are broken as well as long as the public key is not updated?

Because as far as I can tell, no updates are being installed as long as the public key issue is unresolved on my system.

I can confirm that Spotify will finally update when running the command in the OP. Though my question still stands..

Hello, I just get an failure massage. Is this key still correct? Thank you for your support

 

They key is already not valid anymore:

Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key E1096BCBFF6D418796DE78515384CE82BA52C83A, which is needed to verify signature.


what happened to the current song playing popup feature?

I wonder why spotify still uses `/etc/apt/trusted.gpg.d` and not `/etc/apt/keyrings` with `deb [signed-by=/etc/apt/keyrings/spotify.gpg]` directive ?

Suggested posts

Let's introduce ourselves!

Hey there you,   Yeah, you! 😁   Welcome - we're glad you joined the Spotify Community!   While you here, let's have a fun game and get…

ModeratorStaff / Moderator/ 4 years ago  in Social & Random