[regression] amarok not recognising multimedia keys

Bug #147616 reported by Patrick
22
Affects Status Importance Assigned to Milestone
KDE Utilities
Unknown
Medium
kdeutils (Ubuntu)
Won't Fix
Low
Unassigned
Declined for Dapper by Harald Sitter
Declined for Hardy by Harald Sitter
Declined for Intrepid by Harald Sitter
Declined for Jaunty by Harald Sitter
Declined for Karmic by Harald Sitter

Bug Description

Hi. In Feisty, amarok started picking up the multimedia keys from my keyboard (a genius one, don't know model), they were put as XF86audioplay, XF86forward and similar, but in gutsy it doesn't happen anymore. The keys are recognised in gnome, since in System -> Preferences -> Shortcuts the are picked up as 0x02 and so.. but in amarok they aren't.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in amarok.

Revision history for this message
Xvani (fredrile+launchpad) wrote :

Confirmed in Gutsy.

Win+C and Win+V do not work out of the box while using Gnome.

Probably a conflict with either keyboard shorcuts or compiz..

I do not believe this is an Amarok specific bug, and might be linked with the Super+L bug in Gnome's "keyboard shortcuts"

Revision history for this message
Xvani (fredrile+launchpad) wrote :

I figured this out.

When using Compiz, "Enhanced Zoom Desktop" is enabled by default. It has assigned the hotkey "Super+C" to Center the mouse. Reassigning compiz keys and/or deselecting the use of "Enhanced Zoom Desktop" solves the problem for that key. I'm betting there are similar settings for the other keys that do not work...

This is really an Ubuntu specific problem, as it does not have a good way to assign global hotkeys...

Revision history for this message
Harald Sitter (apachelogger) wrote :

Changing package to kdeutils since I think Patrick's issue is caused by something in KMilo.

@Xvani: your issue is unrelated to the inital report, please report a bug for compiz asking to change their default shortcuts, since they conflict with Amarok (Applicaton use are more important than Desktop Effects).

Revision history for this message
Toni Filgueras (toni-fiz) wrote :

Same problem here, I changed the keys in compiz but still having problems
Key shortcuts work when amarok window is in focus but they doesn't work when minimized to tray
I've noticed thar win+'x', win+'+', and win + '-' work correctly

Revision history for this message
Graham Clenaghan (origin191) wrote :

This is also the case in hardy, but now the Gnome Multimedia Keys script I was using to patch it no longer helps.

Revision history for this message
BrowneR (chris-scotland) wrote :

I created a script that fixed this with Amarok in feisty/hardy.

A new version of my script "Gnome Multimedia Keys" is available which should now work in Hardy.

This will only fix the multimedia buttons (play, next, stop etc) and not fix other shortcuts (win+x, win+c, etc).

Get it here http://chris.scotland.googlepages.com/ or from the amarok script manager.

Revision history for this message
chris (chris-augmented-reality) wrote :

The same happens in KDE 4 in Intrepid. The multimedia keys on my Dell XPS M1530 used to work in Hardy, but now they only work when Amarok is focused (ie open), running KDE 4.1. The normal keyboard combinations work without any problems.

Revision history for this message
gonetil (gonetil-gmail) wrote :

I have a similar problem here (Ubuntu Intrepid 32 bits). I installed BrowneR's script, and it works. But it only does when Amarok is focused and in front of every windows. If another Window is over Amarok, or if Amarok is hidden in the tray, multimedia keys won't work.
I am using Amarok 2.0.1 on KDE 4.2.00.

Revision history for this message
Andreas Zitzelsberger (az82) wrote :

I can confirm gonetils report with KDE 4.2 and Amarok 1.4.10. For me the forward and backward keys stoppend working with Amarok if the Amarok window isn't focused. The keys are regognized, produce proper events (verified with xev) and work if Amarok is focused.

Revision history for this message
Andreas Zitzelsberger (az82) wrote :

@gonetil: Solution and proper bug for our issue is here: https://bugs.launchpad.net/ubuntu/+bug/285056/comments/15

xteejx (xteejx)
tags: added: regression-release
summary: - [GUTSY] amarok not recognising multimedia keys
+ [regression] amarok not recognising multimedia keys
Revision history for this message
xteejx (xteejx) wrote :

Marking Confirmed, Low. Reported upstream, linking LP to KDE bugtracker.

Changed in kdeutils (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Changed in kdeutils:
status: Unknown → New
Revision history for this message
xteejx (xteejx) wrote :

It hasn't updated here yet, but it's been marked as Resolved. This is fixed in a later version. Requesting a backport for this.

Revision history for this message
xteejx (xteejx) wrote :

Think I may have clicked too many, sorry about that SRU guys.

Changed in kdeutils:
status: New → Invalid
Revision history for this message
Harald Sitter (apachelogger) wrote :

SRU != backport

In order to archive a stable release update the 'fix-in-later-version' needs to be isolated and transformed into a patch against the amarok versions in all Kubuntu versions that ought to obtain the SRU (ultimately attached as a debdiff to this report, to make it easier processable).

Unless some kind of useful patch is attached to the report, all nominations will be rejected as per SRU policy.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

KMilo from KDE3 is unmaintained. For those with similar symptoms in KDE4, this is tracked at bug 223412.

Changed in kdeutils (Ubuntu):
status: Confirmed → Won't Fix
Changed in kdeutils:
status: Invalid → Unknown
Changed in kdeutils:
importance: Unknown → Medium
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.