Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
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!
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:~$ /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=spotify --file-forwarding com.spotify.Client @@u %U @
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
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.
Like Bro, what is UP WITH THE LATEST UI!? https://imgur.com/a/Vcsqoqk Baby fricken blue on black!?
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.
Ask your distributor about it. The Flatpak is not officially supported.
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.
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?
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...
The above constitutes inappropriate handling of GPG keys. Please see my previous post for how to fix this. Thanks.
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…