Bug 204576 - Some sound shortcuts (play, track skip) no longer working in GNOME
Summary: Some sound shortcuts (play, track skip) no longer working in GNOME
Status: CLOSED DUPLICATE of bug 201176
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-30 06:05 UTC by Jens Knutson
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-08-30 06:10:19 UTC


Attachments (Terms of Use)

Description Jens Knutson 2006-08-30 06:05:42 UTC
Description of problem:

The sound shortcut keys I set up in the GNOME Keyboard Shortcuts for
"Play/Pause", "Stop playback", "Skip to previous track", and "Skip to next
track" stopped functioning about a week ago.  (Sorry, was without net access
till now, couldn't file the bug!)

Despite this, the volume and mute shortcuts still work fine.


Version-Release number of selected component (if applicable):

control-center-2.15.92-5.fc6


How reproducible:
100%


Steps to Reproduce:
1. Set up keyboard shortcuts
2. open your media player
3. jab "play" key, song doesn't start playing
  
Actual results:
Nothing happens


Expected results:
media player should toggle play/pause state


Additional info:

They were working fine last week in Muine and Totem (my primary media apps) as
well as Banshee and Rhythmbox.  They no longer work in any of these.

I have tried disabling the shortcuts and re-adding them, as well as trying
completely different keys/key combinations, all to no avail.

Comment 1 Jens Knutson 2006-08-30 06:10:19 UTC

*** This bug has been marked as a duplicate of 201176 ***

Comment 2 Ray Strode [halfline] 2006-08-30 15:34:19 UTC
I have a patch I'm working on to get rhythmbox back in order (then I'm going to
do totem).  I thought Muine would already work, so I'm a bit surprised that it
doesn't.  I'll have to investigate that.


Note You need to log in before you can comment on or make changes to this bug.