Version: 1.4.3 (using KDE 3.5.3, Kubuntu Package 4:3.5.3-0ubuntu0.2 dapper) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.15-27-386 While the default Global shortcuts (such as win+c) work even when Amarok is not in the foreground, as soon as I change it to a custom shortcut, the exact same functionality disappears until I revert to the defaults. The behaviour of the defaults is exactly correct, it is just that I cannot change the shortcut for the desired behaviour. For Example: The default global shortcut for "Next Track" is Win+B. If I change it to what I want (Ctrl+KP_6), I can no longer go to the next track. If I revert back to the default (Win+B) functionality is restored.
Sorry, 1 additional note. The custom shortcut DO work but only when the program is in the foreground. As soon as I switch to something else, the exact shortcut I just used in the program stops working.
Confirmed ... only happens for KP_* keys though.
I can reproduce this as well. But, I don't think it's an Amarok issue. Looks like a KDE issue to me.
Reassign to kdelibs, since it's a KDE Global Shortcut issue (try setting a Ctrl+KP_* shortcut in kcmshell keys -> doesn't work either).
actually reassign :P
What is the status of this bug? Does it still happen with a recent KDE version, such as 4.6.5 or 4.7.x? Please add a comment.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I switched away from KDE a year after I opened this defect. It has been nearly 12 years. I don't use either KDE or Amarok anymore. As far as I know, this issue could still be present or closed. I no longer care. Unless someone else feels like they want to take up the issue, I vote to close this.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!