hardy: multimedia keys no longer work

Forgot to mention: the volume-up, volume-down and mute-buttons work fine.

Thank you for your bug. What version of gnome-control-center do you use?

I have 1:2.21.90-0ubuntu1 installed.

I have gnome-control-center 2.21.90 too, and can confirm this issue since a few days (I upgraded g-c-c on January 31st according to dpkg.log).

emilio@pochu:~$ dpkg -l gnome-control-center capplets-data gnome-settings-daemon libgnome-window-settings1
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=================================-=================================-==================================================================================
ii capplets-data 1:2.21.90-0ubuntu1 configuration applets for GNOME 2 - data files
ii gnome-control-center 1:2.21.90-0ubuntu1 utilities to configure the GNOME desktop
ii gnome-settings-daemon 2.21.90.1-0ubuntu3 GNOME settings daemon
ii libgnome-window-settings1 1:2.21.90-0ubuntu1 Utility library for getting window manager settings
emilio@pochu:~$

Moving the bug to g-c-c as this happens with totem too.

On February 3, 2008 6:58:28 pm Launchpad Bug Tracker wrote:
> You have been subscribed to a public bug:
>
> Binary package hint: rhythmbox
>
> In gutsy, my multimedia keys (Next song, Previous Song, Play/Pause) on
> my Cherry Evolution Stream keyboard worked fine. Since the upgrade to
> hardy, they no longer work for rhythmbox. I re-assigned them with
> System->Settings->Keyboard Shortcuts, but without success.
>
> ** Affects: gnome-control-center (Ubuntu)
> Importance: Low
> Assignee: Ubuntu Desktop Bugs (desktop-bugs)
> Status: Confirmed

Error-I have no keyboard prolems

poningru@rattrap:~$ dbus-monitor
signal sender=org.freedesktop.DBus -> dest=:1.49 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.49"
method call sender=:1.49 -> dest=org.freedesktop.DBus path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='method_call'"
method call sender=:1.49 -> dest=org.freedesktop.DBus path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='method_return'"
method call sender=:1.49 -> dest=org.freedesktop.DBus path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='error'"
signal sender=:1.0 -> dest=(null destination) path=/org/gnome/SettingsDaemon/MediaKeys; interface=org.gnome.SettingsDaemon.MediaKeys; member=MediaPlayerKeyPressed
   string ""
   string "Next"
signal sender=:1.0 -> dest=(null destination) path=/org/gnome/SettingsDaemon/MediaKeys; interface=org.gnome.SettingsDaemon.MediaKeys; member=MediaPlayerKeyPressed
   string ""
   string "Stop"
signal sender=:1.0 -> dest=(null destination) path=/org/gnome/SettingsDaemon/MediaKeys; interface=org.gnome.SettingsDaemon.MediaKeys; member=MediaPlayerKeyPressed
   string ""
   string "Previous"
method call sender=:1.42 -> dest=:1.1 path=/org/gnome/ScreenSaver; interface=org.gnome.ScreenSaver; member=UnInhibit
   uint32 2095046173
method return sender=:1.1 -> dest=:1.42 reply_serial=75
method call sender=:1.42 -> dest=:1.1 path=/org/gnome/ScreenSaver; interface=org.gnome.ScreenSaver; member=Inhibit
   string "Totem"
   string "Playing a movie"
method return sender=:1.1 -> dest=:1.42 reply_serial=76
   uint32 1126924780
method call sender=:1.42 -> dest=:1.1 path=/org/gnome/ScreenSaver; interface=org.gnome.ScreenSaver; member=UnInhibit
   uint32 1126924780
method return sender=:1.1 -> dest=:1.42 reply_serial=77
method call sender=:1.42 -> dest=:1.1 path=/org/gnome/ScreenSaver; interface=org.gnome.ScreenSaver; member=Inhibit
   string "Totem"
   string "Playing a movie"
method return sender=:1.1 -> dest=:1.42 reply_serial=78
   uint32 1205153884

dbus-monitor shows the keys here, too:

...
signal sender=:1.0 -> dest=(null destination) path=/org/gnome/SettingsDaemon/MediaKeys; interface=org.gnome.SettingsDaemon.MediaKeys; member=MediaPlayerKeyPressed
   string ""
   string "Previous"
signal sender=:1.30 -> dest=(null destination) path=/org/gnome/Rhythmbox/Player; interface=org.gnome.Rhythmbox.Player; member=elapsedChanged
   uint32 47
signal sender=:1.0 -> dest=(null destination) path=/org/gnome/SettingsDaemon/MediaKeys; interface=org.gnome.SettingsDaemon.MediaKeys; member=MediaPlayerKeyPressed
   string ""
   string "Next"
signal sender=:1.30 -> dest=(null destination) path=/org/gnome/Rhythmbox/Player; interface=org.gnome.Rhythmbox.Player; member=elapsedChanged
   uint32 48
signal sender=:1.0 -> dest=(null destination) path=/org/gnome/SettingsDaemon/MediaKeys; interface=org.gnome.SettingsDaemon.MediaKeys; member=MediaPlayerKeyPressed
   string ""
   string "Play"
...

I also have this issue. This seems a regression caused by the fix to bug #182704 (shortcuts don't work when NumLock is on).

That's because the dbus interface changed and the software using it needs to be updated

This bug was fixed in the package rhythmbox - 0.11.4-0ubuntu4

---------------
rhythmbox (0.11.4-0ubuntu4) hardy; urgency=low

  * debian/control.in:
    - recommends on python-coherence (LP: #160592)
    - use the new libsoup version
  * debian/patches/81_from_redhat_use_new_libsoup_version.patch:
    - change from redhat, update the code to the new libsoup version
  * debian/patches/82_from_bugzilla_use_new_key_naming.patch:
    - change from bugzilla to get multimedia key working (LP: #188702)

 -- Sebastien Bacher <email address hidden> Wed, 06 Feb 2008 18:49:12 +0100

Everything's working, except play/pause and stop.
Rhythmbox compiled from svn, synaptic says 0.11.4-0ubuntu4

You should use bugzilla to report svn bugs and not launchpad, the ubuntu package works correctly

The rhythmbox from Hardy is actually working.

Thanks!

Totem multimedia keys are working again

On Do, 2008-02-28 at 14:50 +0000, Tobias Wolf wrote:
> ** Also affects: quodlibet-plugins (Ubuntu)
> Importance: Undecided
> Status: New
>

Why do you think quodlibet is affected? Quodlibet-plugins are working
for me since 20070625-1ubuntu2, for more information see bug 188311.

Seems like Listen is also affected.

Bug #197405

This has been fixed for me with today's updates. Thank you.

Hi, I have never noticed any problem with rhythmbox, but since I installed Hardy banshee has ignored the play/pause, next, previous multimedia keys. This prevents me from using banshee, which is a shame because it seems to have maturated a lot since the last time I tried it. Do you plan to fix it (the importance is "Undecided" for banshee) anytime soon?

Same here... Banshee doesn't recognize the multimedia keys, even after reconfiguring them....
What works is Mute, Volume down, Volume Up, and a MediaDirect button (in a dell inspiron 1405) which i configured to open Banshee.
The rest Prev, Next, Play and Stop, don't work.
I'm using hardy with the latest updates.
I hope there is a fix for the issue.

This seems fixed on hardy. I can't tell what update did the job since I have just tried. Now all multimedia keys are working with banshee (and they still work for rhythmbox).

Thank you

I know for a fact that Banshee 1.0 Alpha 1 has fixed multimedia key support. Can't tell about the Banshee in the repository though.

It's fixed in hardy, upstream trunk and upstream's stable branch.

I would wish to add that Sonata - MPD Front end is also affected. It was working fine in Gutsy. Its only the Play, Pause, Next, Forward and Stop keys that are not working. Volume Up, Down and Mute are working fine.

If we Include the Decibel audio player package to the affected packages, then the #201278 can be marked duplicate

https://bugs.launchpad.net/ubuntu/+source/sonata/+bug/201278

Fix for Exaile released with 0.2.12

decibel-audio-player fixed in Debian, will ask for a sync

Confirming the fix for Exaile 0.2.12. Maybe we should follow the idea in https://bugs.launchpad.net/ubuntu/+source/exaile/+bug/209411 ?

decibel-audio-player synced from Debian

decibel-audio-player (0.09-2) unstable; urgency=low

  * debian/patches/fix_multimedia_keys.dpatch:
    - Added, fix multimedia keys with latest gnome-settings-daemon, as it
      has changed the interface.
  * debian/control,
    debian/rules,
    debian/patches/00list:
    - Add dpatch magic.
  * debian/copyright:
    - Add 'Copyright (C)' so that lintian doesn't complain of a missing
      copyright holder.

 -- Emilio Pozuelo Monfort <email address hidden> Fri, 28 Mar 2008 17:52:51 +0100

In exaile 0.2.11.1-0ubuntu2 on hardy, neither play/pause, or previous/next track hotkeys work on gnome.

I've tested exaile 0.2.13~hardy0~ppa1 and the problem is fixed in this version.

That version can be downloaded on
http://ppa.launchpad.net/exaile-devel/ubuntu/pool/main/e/exaile/

Is it the case to upload that version on hardy repos?

Tayroni Alves -

Thank you! I can also confirm that the problem is fixed in this version!

I cannot discover any bugs in this release, seems completely stable.

Repos please?

Stopped working for Listen again on an up-to-date Hardy.

Sorry, I don't know what could have possibly caused this, haven't used it in a while.

Here's the output:
$ listen
Error grabbing key 144, 0x830b400
Error grabbing key 153, 0x830b400
Error grabbing key 162, 0x830b400
Error grabbing key 164, 0x830b400
location: /usr/lib/xulrunner-1.9b5/libxpcom.so
before 3

This bug was fixed in the package exaile - 0.2.11.1-0ubuntu3

---------------
exaile (0.2.11.1-0ubuntu3) hardy; urgency=low

  * debian/patches/03_fix_mmkeys.dpatch,
    debian/patches/00list:
    - Added to get Multimedia Keys working (LP: #188702)

 -- Pedro Fragoso <email address hidden> Tue, 08 Apr 2008 03:21:07 +0100

same here - volume up/down and mute keys are working fine but (in sonata) play/pause, stop, next and previous track are not working.

http://sonata.berlios.de/changelog.html shows that this bug was fixed in version 1.5, but the most recent version in Ubuntu is 1.4.2. I installed sonata from source and the problem appears to be fixed.

https://bugs.launchpad.net/ubuntu/+source/sonata/+bug/221775 also appears to be a duplicate.

This bug has resurfaced for me (but in a different form, perhaps?). I do not see any org.gnome.SettingsDaemon.MediaKeys events in my D-Bus connection, and my xmodmap is configured exactly as in Hardy.

On Fri, 2008-11-07 at 05:21 +0000, Paul Fisher wrote:
> This bug has resurfaced for me (but in a different form, perhaps?). I do
> not see any org.gnome.SettingsDaemon.MediaKeys events in my D-Bus
> connection, and my xmodmap is configured exactly as in Hardy.
>
Configure your media keys in System->Preferences->Keyboard Shortcuts,
not using xmodmap. gnome-settings-daemon listens to a key combination
specified in gconf.
--
Chow Loong Jin

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hyperair wrote, On 07/11/08 05:19 AM:
> Configure your media keys in System->Preferences->Keyboard Shortcuts,
> not using xmodmap. gnome-settings-daemon listens to a key combination
> specified in gconf.
I have the media keys that I *specified* in xmodmap configured in
Gnome's keyboard shortcut preferences. So Play -> XF86AudioPlay (= my
Thinkpad key combo) and so on. xev confirms they are being sent, and
preferences haven't changed since Hardy. I suppose this bug (if it is
one) doesn't belong with rhythmbox...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkUWH0ACgkQmMA16XtB9goExQCcCVTMFEiXG6wopa/FFy2E4KLI
36kAoJiILc9B8M9Q2OaGlFdMMjkHLd3P
=FsMk
-----END PGP SIGNATURE-----

On Fri, 2008-11-07 at 15:02 +0000, Paul Fisher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> hyperair wrote, On 07/11/08 05:19 AM:
> > Configure your media keys in System->Preferences->Keyboard Shortcuts,
> > not using xmodmap. gnome-settings-daemon listens to a key combination
> > specified in gconf.
> I have the media keys that I *specified* in xmodmap configured in
> Gnome's keyboard shortcut preferences. So Play -> XF86AudioPlay (= my
> Thinkpad key combo) and so on. xev confirms they are being sent, and
> preferences haven't changed since Hardy. I suppose this bug (if it is
> one) doesn't belong with rhythmbox...
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkkUWH0ACgkQmMA16XtB9goExQCcCVTMFEiXG6wopa/FFy2E4KLI
> 36kAoJiILc9B8M9Q2OaGlFdMMjkHLd3P
> =FsMk
> -----END PGP SIGNATURE-----
>

No it doesn't. It belongs to gnome-settings-daemon.

  affects ubuntu/gnome-settings-daemon
--
Chow Loong Jin

A few more details: I'm on Intrepid, with g-s-d 2.24.0-0ubuntu3

could you explain why you think that's a gsd issue?

On Wed, 2008-11-12 at 13:22 +0000, Sebastien Bacher wrote:
> could you explain why you think that's a gsd issue?
>
> ** Changed in: gnome-settings-daemon (Ubuntu)
> Importance: Undecided => Low
> Status: New => Incomplete
>
Because gsd is what listens to the keyboard for stuff. I've experienced
a similar issue before, but that was with a bluetooth phone acting as a
remote control. With Hardy, it worked. Control+P would trigger the media
key "Play", and pressing the button on the phone which fires out Control
+P also triggers the media player. However, in Intrepid, although
xmodmap indicates that the key has been grabbed, nothing happens.
Control+P on the notebook keyboard still works.
--
Chow Loong Jin

Sebastien Bacher wrote, On 12/11/08 08:22 AM:
> could you explain why you think that's a gsd issue?
I've watched the DBus output from gnome-settings-daemon, and it sends
nothing when I press the media keys, as programmed in the Gnome keyboard
preferences. xev confirms that the keypresses are actually being sent.

On Wed, 2008-11-12 at 15:21 +0000, Paul Fisher wrote:
> Sebastien Bacher wrote, On 12/11/08 08:22 AM:
> > could you explain why you think that's a gsd issue?
> I've watched the DBus output from gnome-settings-daemon, and it sends
> nothing when I press the media keys, as programmed in the Gnome keyboard
> preferences. xev confirms that the keypresses are actually being sent.
>
xev should show something like this in the event of gsd actually
capturing your keys:
KeymapNotify event, serial 34, synthetic NO, window 0x0,
    keys: 123 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0

Otherwise it isn't.
--
Chow Loong Jin

hyperair wrote, On 12/11/08 10:36 AM:
> xev should show something like this in the event of gsd actually
> capturing your keys:
> KeymapNotify event, serial 34, synthetic NO, window 0x0,
> keys: 123 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> 0
> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> 0
>
> Otherwise it isn't.

Right. The following is the output from xev:

> KeyPress event, serial 30, synthetic NO, window 0x5000001,
> root 0x6e, subw 0x0, time 660660, (537,100), root:(549,212),
> state 0x10, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
> XKeysymToKeycode returns keycode: 162
> XLookupString gives 0 bytes:
> XmbLookupString gives 0 bytes:
> XFilterEvent returns: False
>
> KeyRelease event, serial 33, synthetic NO, window 0x5000001,
> root 0x6e, subw 0x0, time 660732, (537,100), root:(549,212),
> state 0x10, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
> XKeysymToKeycode returns keycode: 162
> XLookupString gives 0 bytes:
> XFilterEvent returns: False
D-Bus is silent.

On Wed, 2008-11-12 at 16:05 +0000, Paul Fisher wrote:
> hyperair wrote, On 12/11/08 10:36 AM:
> > xev should show something like this in the event of gsd actually
> > capturing your keys:
> > KeymapNotify event, serial 34, synthetic NO, window 0x0,
> > keys: 123 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> > 0
> > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> > 0
> >
> > Otherwise it isn't.
>
> Right. The following is the output from xev:
>
> > KeyPress event, serial 30, synthetic NO, window 0x5000001,
> > root 0x6e, subw 0x0, time 660660, (537,100), root:(549,212),
> > state 0x10, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
> > XKeysymToKeycode returns keycode: 162
> > XLookupString gives 0 bytes:
> > XmbLookupString gives 0 bytes:
> > XFilterEvent returns: False
> >
> > KeyRelease event, serial 33, synthetic NO, window 0x5000001,
> > root 0x6e, subw 0x0, time 660732, (537,100), root:(549,212),
> > state 0x10, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES,
> > XKeysymToKeycode returns keycode: 162
> > XLookupString gives 0 bytes:
> > XFilterEvent returns: False
> D-Bus is silent.
>
Reconfigure Keyboard Shortcuts. Things might have changed from Hardy.
gsd isn't picking up your key at all.
--
Chow Loong Jin

hyperair wrote, On 12/11/08 11:15 AM:
> Reconfigure Keyboard Shortcuts. Things might have changed from Hardy.
> gsd isn't picking up your key at all.
I tried that before; it didn't work.

> From: <email address hidden>> To: <email address hidden>> Date: Wed, 12 Nov 2008 13:22:47 +0000> Subject: [Bug 188702] Re: hardy: multimedia keys no longer work>> could you explain why you think that's a gsd issue?>> ** Changed in: gnome-settings-daemon (Ubuntu)> Importance: Undecided => Low> Status: New => Incomplete>> --> hardy: multimedia keys no longer work> https://bugs.launchpad.net/bugs/188702> You received this bug notification because you are a direct subscriber> of the bug.>> Status in Exaile: Fix Released> Status in “banshee” source package in Ubuntu: Fix Released> Status in “decibel-audio-player” source package in Ubuntu: Fix Released> Status in “exaile” source package in Ubuntu: Fix Released> Status in “gnome-settings-daemon” source package in Ubuntu: Incomplete> Status in “listen” source package in Ubuntu: Fix Released> Status in “quodlibet-plugins” source package in Ubuntu: Fix Released> Status in “rhythmbox” source package in Ubuntu: Fix Released> Status in “sonata” source package in Ubuntu: Fix Released> Status in “totem” source package in Ubuntu: Fix Released>> Bug description:> Binary package hint: rhythmbox>> In gutsy, my multimedia keys (Next song, Previous Song, Play/Pause) on my Cherry Evolution Stream keyboard worked fine. Since the upgrade to hardy, they no longer work for rhythmbox. I re-assigned them with System->Settings->Keyboard Shortcuts, but without success.
_________________________________________________________________
Get the next generation of Free Windows Live Services
http://get.live.com

I was subscribed to bug #303921 , and the solution that was presented there not only solved that problem, but also this problem!

The solution that worked for me was to disable "Locate Pointer" in System --> Preferences --> Mouse. I have no idea why that setting has anything to do with this, but disabling it worked perfectly for me...

Thanks to Toby Bartels for the solution presented in #303921.