https://bugs.kde.org/show_bug.cgi?id=475574

            Bug ID: 475574
           Summary: [Wayland] Unable to bind keys with keycodes above 255
    Classification: Applications
           Product: systemsettings
           Version: 5.27.8
          Platform: Archlinux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: kcm_khotkeys
          Assignee: plasma-b...@kde.org
          Reporter: sidpranjale...@protonmail.com
                CC: k...@michael-jansen.biz
  Target Milestone: ---

SUMMARY

Plasma Wayland session doesn't accept keycodes higher than 255 for
keybinds/custom shortcuts.
I'm aware of it being a limitation on x11, but there's no reason it shouldn't
work on wayland: wev, evtest, and showkey can all detect it (xev can't), it has
a keysym, and even is usable for binds in sway and hyprland, though I know
wlroots and kwin are very different.

The key in question is a laptop vendor specific key, equivalent to the
"PredatorSense" key on Acer Predator series, except it's NitroSense because I
have an Acer Nitro. The keysym is XF86Presentation, according to wev.

STEPS TO REPRODUCE
1. Have a keyboard with a non-standard key.
2. Attempt to use it for a custom shortcut.

OBSERVED RESULT
The key does not register.

EXPECTED RESULT
They key registers.

SOFTWARE/OS VERSIONS
Linux: Kernel 6.5.6
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
evtest output:
Event: time 1697206386.162660, -------------- SYN_REPORT ------------
Event: time 1697206387.304843, type 4 (EV_MSC), code 4 (MSC_SCAN), value f5
Event: time 1697206387.304843, type 1 (EV_KEY), code 425 (KEY_PRESENTATION),
value 1
Event: time 1697206387.304843, -------------- SYN_REPORT ------------
Event: time 1697206387.408437, type 4 (EV_MSC), code 4 (MSC_SCAN), value f5
Event: time 1697206387.408437, type 1 (EV_KEY), code 425 (KEY_PRESENTATION),
value 0

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to