Bug 487958 - Num-lock key not selectable as a shortcut key
Summary: Num-lock key not selectable as a shortcut key
Status: RESOLVED DUPLICATE of bug 422401
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 6.0.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-03 13:11 UTC by Maximilian Böhm
Modified: 2024-06-05 15:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maximilian Böhm 2024-06-03 13:11:23 UTC 
Num-lock key not selectable as a shortcut

I want to use my Num key as a shortcut, it has worked perfectly fine via xbindkeys on X.org but using the native Plasma shortcut UI on Wayland, I cannot use this key, pressing it just doesn’t make any input to the choose button.

EXPECTED RESULT
Register the the Num key as a regular shortcut key.

Linux: Arch
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Comment 1 Maximilian Böhm 2024-06-03 13:35:32 UTC 
Oh, found out it has to do with my keymap German Neo. Switching to regular German makes the Num key selectable (and the shortcut works). But switching again to German Neo, I cannot use the shortcut anymore. The num key gets mapped to Tab. And the KDE shortcut settings don’t seem to override this. Then that’s the actual bug.
Comment 2 Maximilian Böhm 2024-06-03 13:43:44 UTC 
In xbindkeys, my key setting is "c:77". Maybe manually entering it into ~.config/kglobalshortcutsrc might work?
Currently, the line reads:

Toggle Night Color=NumLock,none,Toggle Night Light

But how to enter this specific key code? Is it even the same on Wayland than on X.org?
Comment 3 fanzhuyifan 2024-06-03 22:52:30 UTC 
(In reply to Maximilian Böhm from comment #1)
> Oh, found out it has to do with my keymap German Neo. Switching to regular
> German makes the Num key selectable (and the shortcut works). But switching
> again to German Neo, I cannot use the shortcut anymore. The num key gets
> mapped to Tab. And the KDE shortcut settings don’t seem to override this.
> Then that’s the actual bug.

If the key is unmapped currently we can't do anything about it. In that case this should be marked as a duplicate of either BUG 422401 or BUG 475574.

Is the num-lock key mapped by this keymap you are using? You can check via something like `xmodmap -pke | grep Num_Lock`.
Comment 4 Maximilian Böhm 2024-06-05 11:39:25 UTC 
No, "xmodmap -pke | grep Num_Lock" doesn’t show me anything with German Neo.
Comment 5 fanzhuyifan 2024-06-05 15:12:28 UTC 
(In reply to Maximilian Böhm from comment #4)
> No, "xmodmap -pke | grep Num_Lock" doesn’t show me anything with German Neo.

Marking this as a duplicate of BUG 422401 since the underlying cause is the same -- kde currently cannot deal with unmapped keys.

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