Media keys not user-reassignable since gnome 3.34
Hi there, After upgrading my ubuntu install from 19.04 to 19.10 it seems to have upgrade the version of gnome to 3.34. So now the media keys are being handled by some systemd service? Well without changing anything, some of my existing keyboard shortcuts / bindings stopped working. One of them was alt-tab for switching windows. However after cancelling / re-assigning that one and rebooting the system that has thankfully started working again. What is remaining is my media keys for: volume up, volume down and mute.
I can see that these keys are working and they are appearing in the logs of the gsd-media-keys
systemd service (or tartget, whatever it is). Unfortunately the user assigned shortcuts in my Gnome Settings Daemon control panel (devices --> keyboard) page. The simply are not being respected anymore. I have tried to reassign these ones too. However actually inside the key reassignment dialogue itself it still passes behind the media key and I cannot reassign it!
What happens is that the functions for volume up /down and mute are being sent to whatever the default currently selected pulse audio sound device is. Such as the named pulse device "Jack Sink (PulseAudio Jack Sink) in my specific case. Of course for other people it will be other named pulse devices.
Here is the relevent sections in the journalctl -fxe
output for one single press each of the Volume Up, Volume Down and Volume Mute media keys in turn. To better see what is happening here. As clearly IDK what's going on with this new stuff.
Oct 24 18:38:07 apex gsd-media-keys[27105]: Received accel id 114 (device-id: 1515699, timestamp: 0, mode: 0x0)
Oct 24 18:38:07 apex gsd-media-keys[19674]: gvc_mixer_stream_get_port: assertion 'stream->priv->ports != NULL' failed
Oct 24 18:38:07 apex gsd-media-keys[27105]: Could not find accelerator for accel id 114
Oct 24 18:38:07 apex gsd-media-keys[27105]: Updating client: index=39 name='Native client (UNIX socket client)'
Oct 24 18:38:07 apex gsd-media-keys[27105]: Updating client: index=39 name='libcanberra'
Oct 24 18:38:07 apex gsd-media-keys[27105]: Updating sink: index=1 name='jack_out' description='Jack sink (PulseAudio JACK Sink)' map='front-left,front-right'
Oct 24 18:38:07 apex gsd-media-keys[27105]: Removing sink input: index=3
Oct 24 18:38:10 apex gsd-media-keys[19674]: gvc_mixer_stream_get_port: assertion 'stream->priv->ports != NULL' failed
Oct 24 18:38:10 apex gsd-media-keys[27105]: Received accel id 156 (device-id: 1518987, timestamp: 0, mode: 0x0)
Oct 24 18:38:10 apex gsd-media-keys[27105]: Could not find accelerator for accel id 156
Oct 24 18:38:10 apex gsd-media-keys[27105]: Updating sink: index=1 name='jack_out' description='Jack sink (PulseAudio JACK Sink)' map='front-left,front-right'
Oct 24 18:38:13 apex gsd-media-keys[27105]: Received accel id 151 (device-id: 1522099, timestamp: 0, mode: 0x0)
Oct 24 18:38:13 apex gsd-media-keys[27105]: Could not find accelerator for accel id 151
Oct 24 18:38:13 apex gsd-media-keys[19674]: gvc_mixer_stream_get_port: assertion 'stream->priv->ports != NULL' failed
Oct 24 18:38:13 apex gsd-media-keys[27105]: Updating sink: index=1 name='jack_out' description='Jack sink (PulseAudio JACK Sink)' map='front-left,front-right'
Oct 24 18:38:14 apex gsd-media-keys[27105]: Removing sink input: index=4
Anyhow what I was hoping to link this to instead was some commandline tool, for me to enable setting my master volume in ALSA instead. Which is where my JACK audio and DAW sound is finally getting routed to. And I simply cannot do this in pulse audio. This was my previous setup in 19.04 and earlier and it worked beautifully, simply assigning a custom keyboard shortcut in the gnome settings daemon.
Is there is anything else extra I can add here? To help debug this problem any further? Perhaps other user(s) recent issue is also already raised here, regarding a similar matter. And maybe these new bug reports are somehow related to each other. Kind Regards.