Multimedia keys only works after re-configuring in gnome-keybinding-properties and restarting rhythmbox

Bug #32917 reported by Koen Sadza
28
Affects Status Importance Assigned to Milestone
Rhythmbox
Invalid
Undecided
Unassigned
rhythmbox (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Could also be a gnome-keybinding-properties bug ofcourse...

Tags: keyboard
Revision history for this message
Koen Sadza (koen) wrote :

BTW: This is only for the Play/Pause, Stop, Previous and Next keys (the ones Rhythmbox uses), all the general keys gnome handels are working, such as volume up/down, mut, calculator, mail and homepage.

So I'm actually quite sure it's a rhythmbox bug.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you have the issue with totem by example?

Revision history for this message
Sebastien Bacher (seb128) wrote :

What version of Ubuntu do you use?

Changed in rhythmbox:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Koen Sadza (koen) wrote :

I use dapper, but the bug was already in hoary.

I don't have the issue with totem.

Revision history for this message
Koen Sadza (koen) wrote :

Well I tried to be sure, and I do have the same issue with totem.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Are you sure totem has this issue too? I've been seeing this for years (and still on dapper) and totem picks up play pause key changes straight away whereas rhythmbox does not...

Be warned! totem only responds to keybindings when its window is focused (unlike rhythmbox that always responds whether it unfocussed/minimised/hidden etc.). If rhythmbox is open it will steal the pause button keypresses before totem can get hold of them.

This can be demonstrated by changing keybinding when both totem and rhythmbox are open. Assuming totem is focused it now able to see the new key because rhythmbox has not grabbed yet.

Revision history for this message
Alan Tam (at) wrote :

My problem with today's dapper is that sometimes after I reboot, all the multimedia bindings are not working. I've to go to gnome-keybindings-properties to remove them and set them again, and then restart totem/rhythmbox to make them work.

Revision history for this message
Koen Sadza (koen) wrote :

Since a week or so,
they aren't working at all, not even the volume keys,
not on my notebook-keyboard, not on my logitech keyboard...

Revision history for this message
Hidde Brugmans (hcbrugmans-deactivatedaccount) wrote :

I've seen some odd behavior here too, almost certainly not a rhythmbox problem however.

Volume up/down used to go fluently, now it goes in steps, and sometimes it does not work at all.
Something was changed here.

Revision history for this message
Miek Gieben (miek) wrote :

Set the 'skip to next track' to control-shift-plus. RB doesn't pick this up
at all.
While fiddling with I somehow managed to set this shortcut to 'n'. This was
picked up by RB, but leaves me with the letter n :-(

So looks to be an issue with the modifier keys?

Revision history for this message
Carl van Tonder (carlvantonder) wrote :

As to the original bug, I experience this off a fresh dapper install as of yesterday, and have had it in every dapper install since midway through the dapper dev process.

Revision history for this message
Andrew Conkling (andrewski) wrote :

This is still happening in 6.06.

Changed in rhythmbox:
status: Needs Info → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Should probably be forwarded upstream

Changed in rhythmbox:
importance: Medium → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

Does anybody have that bug on feisty?

Revision history for this message
LeighWebber (webbber) wrote : Re: [Bug 32917] Re: Multimedia keys only works after re-configuring in gnome-keybinding-properties and restarting rhythmbox

no - i think its working fine - but then i have very much become a KDE
power user since i filed the bug - and i may have subconsciously
mapped keys... but i think its working ok! I had a problem when i was
using aiglx/beryl - but since i've stopped (becasue of the recent bug
in feisty) its all good.

regards

leigh

On 2/22/07, Sebastien Bacher <email address hidden> wrote:
> Does anybody have that bug on feisty?
>
> --
> Multimedia keys only works after re-configuring in gnome-keybinding-properties and restarting rhythmbox
> https://launchpad.net/bugs/32917
>

--
Leigh Webber
http://leighwebber.co.uk

Revision history for this message
Kieran Hogg (xerosis) wrote :

Before the rhythmbox patch to work with control-centre (off the top of my head) it was not working but it has been since that patch.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for the update, marking fixed then

Changed in rhythmbox:
status: Confirmed → Fix Released
Revision history for this message
Andrew Conkling (andrewski) wrote :

The keys are similarly broken in Banshee; filed separately as bug #87299.

Revision history for this message
diehorsti (oszwald-deactivatedaccount) wrote :

Upgraded to feisty fawn from edgy eft. Used .gconf from edgy eft. As audiosink esdsink is entered with gconf-editor for both music and audio. Starting rhythmbox. Hitting Volume up/down brings new transparent loudspeaker popping up. volume slider in tray changes volume. The voume slider in rhythmbox doesn't move at all. Volume that is heard over stereo doesn't change at all. Same behaviour in totem. Any ideas? Thanks in advance. Cheers.

Revision history for this message
Arwyn Hainsworth (arwyn) wrote :

Just to confirm that this bug is indeed fixed on feisty on my machine.

diehorsti: what you described sounds like your main volume control is set to a different channel to rhythmbox. Since this isn't a bug per-say, for further advise in how to solve your problem I suggest you use the support mailing list <email address hidden>

Changed in rhythmbox:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.