Type in your question below and we'll check to see what answers we can find...
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.
Please see below the current ongoing issues which are under investigation.
Loading ongoing issues...
Debian with Unstable Updates
My Question or Issue
The Media Keys Play/Pause/Next/Previous on the keyboard don't work with the Spotify Application.
The Media Keys work with other applications in Linux such as Clementine and also work with the Spotify Application in Windows just fine. I would think it should be easy to make the media keys work just like they do in Clementine and other media applications in Linux.
I found that the suggestion to use mpris-control did exactly what I wanted, and this is no longer problematic for me.
EDIT: my bad. reboot fixed it
The latest snap update 184.108.40.206.gf614956d-16 is not with media keys too on Kubuntu 19.04. It worked with the previous versions (but that couldn't play local files due to a bug). Spotify doesn't show up in the media player widget
Spotify 220.127.116.110.g51b03ac3 . Running on Gentoo with Plasma desktop. All media players and browsers work flawlessly with media keys, not Spotify. Alternate media shortcuts via D-Bus commands is a nasty hack. Please address this.
tnx so much
I'm using Spotify 18.104.22.1686.ge08ef575 on Manjaro Linux. The browser and other software work well with media keys, not Spotify. Please fix this issue.
There are several items which cause the media-keys not to work.
One is that chrome/chromium can also hijack these key's when you use youtube.
The systems then doesn't know which player to select and it can fail.
I have created a small utility which you can download from github:
I created a special shortcut by using the super+media-keys which work only for spotify by using `mpris-control -t Spotify toggle` for example.
If you find any bugs, please report that at the issues section.
You are right... killing chrome solves the issue. It seems that chrome does not release the keys when youtube is closed (if there is such a thing). Thanks.
How is this still an issue? Spotify, you're a down right travesty. UX, who does that?
Actually the issue isn't attached by the Ubuntu version, but the desktop environment. The media keys does not works in Unity desktop (Ubuntu 16.04 default), but works in others desktops, like Gnome shell(Ubuntu 18.04 default). For example, if you install gnome session in Ubuntu 16.04, the keys will works perfectly
EDIT: Never mind, I spoke too soon! Issue persists.
It seems the issue is finally fixed! My media keys are suddenly working again. 🙂
I'm glad to hear that. Now I just have to remember to to deactivate the workaround on my affected laptop.
Actually, I don't know what happened but the issue still persists. Sorry for the false hope!
There is nothing Spotify can do, except maybe for modifying there player name to 0Spotify or something which maybe gets it sorted at the top of the dbus list.
When you encounter issues with your media-keys execute the following command and look at the result:
dbus-send --session --dest=org.freedesktop.DBus --type=method_call --print-reply /org/freedesktop/DBus org.freedesktop.DBus.ListNames | grep 'org.mpris'
It will probably show that there is an other player also active, and possibly with a letter earlier in the alphabet then the S from Spotify.
To mitigate this at least for your self you could close this other player or use a tool i created which i posted a few posts back which you can use to bind it to Spotify it self.
Don't think media keys depend on name order. From my experience, it really only controls the app that started first. A quick fix is to start Spotify after you boot and leave it there. Media keys will always work for Spotify in this case. As you have mentioned, this isn't something the Spotify app can do to remediate.
Excellent tip about looking-up the DBus mpris registry entries. I usually have the opposite problem. If I have both Spotify and Clementine running (I use Clementine for certain radio stations not available in Spotify) Spotify responds to the media buttons but not Clementine. If I close Spotify then Clementine responds to the media buttons.
I was inspired to build on your DBus command, this will yield the process ID as well as the DBus name. This will make it easier to pin-point the culprit using your process viewer.
DBus Media Player & PID
for qualifiedName in `dbus-send --session --dest=org.freedesktop.DBus --type=method_call --print-reply /org/freedesktop/DBus org.freedesktop.DBus.ListNames | sed -n 's/.*"\(org\.mpris\..*\)"/\1/p'` do printf "$qualifiedName\t"; dbus-send --session --print-reply --dest=org.freedesktop.DBus / org.freedesktop.DBus.GetConnectionUnixProcessID string:$qualifiedName | sed -n 's/^[[:space:]]*uint32 \([0-9]*\)$/\1/p' done
org.mpris.MediaPlayer2.clementine 24870 org.mpris.MediaPlayer2.spotify 19718 org.mpris.clementine 24870
I can then use System Activity to track-down these processes (screenshot attached).
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game…