Child Item

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!

Child Item

Accepted answers

All comments

i440bx

Hi Vasil,

Today, my Spotify client told me that it doesn't want to run anymore. I'm using Debian 13 Trixie with the Spotify client in a Flatpak container. The command to run the client is:

robert@robert:~$

Today, I was surprised by this error code:
robert@robert:~$ (spotify:7): libayatana-appindicator-WARNING **: 12:56:07.781: libayatana-appindicator is deprecated. Please use libayatana-appindicator-glib in newly written code.libc++abi: terminating due to uncaught exception of type std::out_of_range: unordered_map::at: key not found

---

It looks exactly like the new key I need soon, but it doesn't solve the problem. My client still won't start. Can you help me with a command for Flatpak users?

My Client has version 1.2.74.477.g3be53afe and was updated at 11/19/2025.

Thanks,
Robert

WalterGinsberg

Will this impact the many of us who refuse to upgrade because of the terrible UI changes? Our request to restore the queue has been ignored for nearly two years.

Mikel090897

Like Bro, what is UP WITH THE LATEST UI!? https://imgur.com/a/Vcsqoqk Baby fricken blue on black!?

i440bx

Oha, we just made an family account....

@Spotify are you like Apple and **bleep** about the wishes of your customers?

---

I was able to "solve" the problem with the missing key by reinstalling the client. Lets see what happens after the next update.

fabiscafe

Ask your distributor about it. The Flatpak is not officially supported.

fabiscafe

Wayland requires a Client Side Decoration (CSD), this is Spotifys fallback for now. If your desktop environment supports Server Side Decoration(SSD)enable them to remove it.

RDCallahan86

I am still on Debian 12 and Spotify was working 100% fine this morning, lossless, all my library, songs etc. Then I get an update and it won't even load. I tried adding the new key and that didn't resolve it. I guess I will just uninstall?

TMM55

Latest version is broken on Debian 12 and derivatives: https://community.spotify.com/t5/Desktop-Linux/New-version-from-Debian-repo-requires-GLIBC-2-38/td-p/7260853

Perkelix

The above constitutes inappropriate handling of GPG keys. Please see my previous post for how to fix this. Thanks.

AJ_130

I don't understand,you wanted me to prove to you that I'm not a robot?

VadimP2

Thanks for putting out Spotify for Linux, folks! Appreciate the work you put into this in your spare time.

marcoshalano

I created a topic about this visual problem. First happened to me with snap version, but someone else reported that also happens in the native version. I added screenshots: https://community.spotify.com/t5/Desktop-Linux/Snap-version-without-themed-window-bar/m-p/7300762#M24456

superoscar1759

i just got an update today and now it looks like that.

Does it still look like that for you? did you do a snap or deb installation?

marcoshalano

I'm using the .deb package. The revision 92 of the Snap has this problem. The previous review, 89 didn't have.

ghhfgh

感謝你們推出 Linux 版 Spotify！非常感謝你們利用空閒時間為此付出的努力。

remarek

For any folks looking to rollback to a previous Spotify flatpak client without the new blue bar window decoration, I've had success by first downgrading to a previous version with the command:

sudo flatpak update com.spotify.Client --commit=6daa559db754864d93170313d42ba50642137fae5aa16b25b92dbf37fdfe252d

Then using a flatpak manager application like Flatseal - enabling the X11 windowing system for the app and turning off wayland for it. Hope this helps anyone!

Pajaspastiller

I updated the key with the instructions above but still get an error (Debian 13). Am I doing something wrong? This is the error I get:

Varning: An error occurred during the signature verification. The repository is not updated and the previous i
ndex files will be used. OpenPGP signature verification failed: https://repository.spotify.com stable InReleas
e: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key E1096BCBFF6D418796DE78515384CE82BA52C83A, which is needed to verify signature.

Pajaspastiller

So apparently I had some old location for the key in the /etc/apt/sources.list.d/spotify.list when I edited it to [signed-by=/etc/apt/trusted.gpg.d/spotify.gpg] it is working again

OliverCalder

The problem with the light blue titlebar is that those are the Spotify-provided Client-Side Decorations (CSDs). With the switch to native Wayland in the new Spotify release (snap, .deb, flatpak (which is built from the snap)), CSDs are now used instead of Server-Side Decorations (SSDs).

The issue can be hidden by forcing XWayland, which can be done by adding --ozone-platform=x11 to the Exec= line in the .desktop file. But this should be done by whoever packages the Spotify builds for Linux.

The real solution would be for the Spotify build for Linux to update it's CSDs to match what it provides on Windows and MacOS.

Discussed more here (see page 2): https://community.spotify.com/t5/Desktop-Linux/Snap-version-without-themed-window-bar/m-p/7300762

Ibraheem94

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

Nostalgia_Realm

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..

TPom

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

GeekBoy03

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.

Jaxius

what happened to the current song playing popup feature?

burtek

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 ?

Perkelix

@burtek I already filed a ticket about that: https://community.spotify.com/t5/Desktop-Linux/Debian-packaging-could-use-some-upgrading/m-p/6820748#M23526

b87d_-ce745qm

app stopped working after yesterday's update. Message saying that 'spotify cannot play this at the moment'. Already cleared cache and did a fresh app reinstall.

pgomes

I have updated this thread about the window decoration issue in Wayland. In summary: it should be fixed soon

zviryatko

hello, just thanks for last update, finally got fixed window decoration issue on wayland and which is more important for me - close to tray. Found that I didn't use spotify on pc for a few months since it was broken. 🙏

emanemanovic

Hi everyone,

Like many of you in this thread, I just ran into the same Sub-process /usr/bin/sqv returned an error code (1) and Missing key E1096BCBFF6D418796DE78515384CE82BA52C83A errors when trying to run sudo apt update.

While providing manual curl workarounds in this forum is helpful as a quick fix, it doesn't solve the core issue. I'd like to kindly ask the Spotify Linux engineering team to consider a permanent solution to this recurring problem.

Every time the GPG signing key for repository.spotify.com rotates/expires, it completely breaks the system-wide update process for Debian, Ubuntu, and Linux Mint users who rely on the native .deb client. This creates a lot of unnecessary frustration and forces users to hunt for the newest hash on forums to run complex CLI commands manually.

Feature Request: Automatic APT GPG key rotation

Could the Spotify team please implement an automated key rotation mechanism by shipping a dedicated keyring package? Other software vendors (like Grafana, Docker, or InfluxData) handle this seamlessly.

If you shipped a spotify-archive-keyring .deb package that installs directly to /etc/apt/keyrings/spotify.gpg, you could simply push an update to this keyring package signed with the old key a few weeks before it expires. The update would quietly place the new key on our systems in the background. When the old key finally expires and the new one takes over the repository, the new key would already be locally trusted.

This approach completely eliminates the broken apt update experience and aligns with current Debian/Ubuntu security best practices (avoiding apt-key deprecation warnings and keeping keys properly isolated).

Thanks to the devs for maintaining the Linux client (we really appreciate having it!), but please consider smoothing out this packaging workflow.

Best regards,

Jakub

Child Item

#themeFooter{display:none!important}