Plan
Free
Country
USA
Device
(Desktop PC)
Operating System
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.
EDIT: my bad. reboot fixed it
The latest snap update 1.1.5.153.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 1.0.80.480.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 1.1.10.546.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:
https://****/BlackDex/mpris-control/releases
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.
ORIGINAL:
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'
doneExample
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).
Thank you, bro! Media keys started to work after I had disabled "Hardware Media Key Handling" from Google Chrome.
I finally found the way to have it working (if you are a Chrome browser user), whether with deb package or snap on Ubuntu 19.10.
First of all check in Settings > Devices > Keyboard Shortcuts that your Media Keys are present (release update from 19.04 to 19.10 set them all to Disabled in my case)
Then open Chrome browser :
Deal.
Yes, problem was Chrome's hardware media key handling for me, too.
UPDATE: I'm on Plasma desktop, and removed a long-used widget "Compact Media Player" in favor of the bundled Media Player widget. And suddenly all media key interaction works. System audio mute, previous, play/pause, next, etc. Keep this in mind if you're here looking for answers.
Worked perfectly. Problem wasn't spotify at all, but chrome messing using the keys!
I'm using KDE (and Firefox, not Chrome if this matters) and found another problem why it was not working: the media player Clementine overwrote the global shortcuts to control the current media player.
Go to Settings > Global shortcuts > Media controls and reassign the keys. Works for me again.
I can confirm disabling media key handling on Chrome fixes this.
Weird thing is that I had no media being played on Chrome, so maybe this is a Chrome bug instead?