Bug 367953

Summary:	Global shortcuts not working on modified keys
Product:	[Frameworks and Libraries] frameworks-kglobalaccel	Reporter:	Emil Sedgh <emilsedgh>
Component:	general	Assignee:	Martin Flöser <mgraesslin>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kdelibs-bugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Emil Sedgh 2016-08-29 10:52:40 UTC

In KDE4, I used to make 'Caps Lock' act like Numlock.

Then numlock was set to enable a global shortcut key.

This doesn't work in Plasma 5 anymore.

Reproducible: Always

Steps to Reproduce:
1. Open up System Settings -> Input Devices -> Keyboard -> Advanced -> Caps Lock Key behavior
2. Open it up and enable 'Make Caps Lock key an additional Num Lock
3. Now go to any app and define a global shortcut. Press Caps Lock as the shortcut key. Num Lock is properly defined.
4.  Save it
5. Press Caps Lock to trigger the shortcut

Actual Results:  
Nothing happens

Expected Results:  
The caps lock key, which is acting like a numlock, should trigger the action.

Comment 1 Martin Flöser 2016-08-29 11:23:48 UTC

could you please specify which version of kglobalaccel and which version of Qt you are using?

Comment 2 Emil Sedgh 2016-08-29 15:25:02 UTC

Hey Martin.

I'm using Debian packages.

Qt 5.6.1
kglobalacces 5.23.0

I used to build KDE manually until a few months ago and this issue was always there (beginning from KF5 times)

Comment 3 Martin Flöser 2016-08-30 05:47:32 UTC

Can you try restarting kglobalaccel after changing the keyboard layout to have numlock as a key.

Btw. I'm not sure whether one can use numlock at all as a global shortcut. It might have been a bug that this worked on Qt 4.

Comment 4 Emil Sedgh 2016-08-30 09:58:45 UTC

Killing kglobalaccel5 and restarting it does fix the issue.

Comment 5 Martin Flöser 2016-08-30 11:53:37 UTC

ok, so this seems to be a case related to not getting the right layout. I think we already have a bug report about it, but cannot find it right now :-(

Comment 6 Emil Sedgh 2016-08-30 17:11:52 UTC

I'm such a fool.

I had this reported already (#351198)  exactly one year ago.

And that was marked as a duplicate of #350816 which is the bug you are referring to.

Thanks again and sorry for the time you had to waste on this.

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