PLAY_PAUSE_KEY events not routed to notify-osd

[Nicolò Chieffo]

Binary package hint: notify-osd

In the spec the PLAY_KEY and PAUSE_KEY are handled by notify-osd to show some icons. Did you forget the PLAY_PAUSE_KEY (not only in the spec, but also in the code)? it's very frequent in laptops!
Next and previous are working correctly

[Mirco Müller (macslow)]

Again, this is not a bug in notify-osd. It should be filed against rhythmbox, banshee and any other media-playing app that's meant to react on these mm-keys... and wants to comply to the new notification guidelines/spec.

[Nicolò Chieffo (yelo3)]

thanks mirco, and sorry. i've added the correct packages to this bug

[Chow Loong Jin (hyperair)]

On Thu, 2009-03-19 at 15:41 +0000, Nicolò Chieffo wrote:
> thanks mirco, and sorry. i've added the correct packages to this bug
>
> ** Also affects: banshee (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Also affects: rhythmbox (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Summary changed:
>
> - PLAY_PAUSE_KEY not handled
> + PLAY_PAUSE_KEY events not routed to notify-osd
>
Shouldn't this be handled by gnome-settings-daemon instead? Perhaps
after it successfully sends the request to be handled, it spits out a
notification?
--
Chow Loong Jin

[Nicolò Chieffo (yelo3)]

Well you are totally right. NEXT_KEY and PREVIOUS_KEY are sending
notifications even if the music player is off. so I will open a bug to
gnome-settings-daemon

[Andrew Conkling (andrewski)]

Bug 343261 covers this for notify-osd and various music players, including Banshee. I'll update the description there to be clear that Play/Pause are covered, not just track changes.