Bug 795052

Summary: Multimedia keys doesn't work with any player but Rhythmbox
Product: [Fedora] Fedora Reporter: Miguel Mora <mik.es.mora>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 16CC: maxamillion, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 20:23:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Miguel Mora 2012-02-18 23:59:16 UTC
Description of problem:
I have a Toshiba s5955 laptop. When I use the multimedia keys with Rhythmbox, everything runs ok. But when I try to use the keys with Amarok, them doesn't work.Also happens the same if I try to use with VLC, dragon player, juK or any other media player.
A dark square appears displaying a forbidden sign when I press play/pause, forward, previous or stop. Also the key assigned to open predetermined media player doesn't work.
I haven't the same problem with previous versions of Fedora or Gnome.

The keys work if I open both players, and works for both at the same time. But if I close rhythmbox, the forbidden OSD sign appears again and the keys stop working.

Version-Release number of selected component (if applicable):
GNOME 3.2.1
gnome-shell 3.2.2.1
Rhythmbox 2.90.1

How reproducible:

Always

Steps to Reproduce:
1.Press a media key, like Play when Amarok is open.
2.Does nothing but displays an OSD square with a forbidden sign.
3.
  
Actual results:
Can't use the keys with any other media player but Rhythmbox

Expected results:
Use media keys with Amarok and VLC, at least, without opening Rhythmbox.

Additional info:
I have installed the script Multimedia Keys on Amarok to allow them working, but nothing happens.

Comment 1 Miguel Mora 2012-02-19 00:03:39 UTC
I have founded this one:
https://bugzilla.redhat.com/show_bug.cgi?id=756592
but doesn't have any solution.

Comment 2 lores000 2012-03-26 22:51:52 UTC
Same here: Amarok ignores the multimedia keys (Fedora 16, Gnome Shell).

Comment 3 Fedora End Of Life 2013-01-16 16:33:52 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-13 20:23:15 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.