Summary: | Num-lock key not selectable as a shortcut key | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Maximilian Böhm <mabo> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | fanzhuyifan, kde, mabo |
Priority: | NOR | ||
Version: | 6.0.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Maximilian Böhm
2024-06-03 13:11:23 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. 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? (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`. No, "xmodmap -pke | grep Num_Lock" doesn’t show me anything with German Neo. (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 *** |