https://bugs.kde.org/show_bug.cgi?id=503230
Bug ID: 503230
Summary: Can't bind KEY_PROG2 as shortcut
Classification: Applications
Product: systemsettings
Version: 6.3.4
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: kcm_keys
Assignee: plasma-b...@kde.org
Reporter: luca.stefani....@gmail.com
CC: duha.b...@gmail.com, fanzhuyi...@gmail.com,
k...@david-redondo.de
Target Milestone: ---
SUMMARY
Binding/adding a new shortcut combo that uses the KEY_PROG2 event code isn't
registered.
KEY_PROG{1,3,4} are working as expected and get mapped to Launch{1,3,4}
respectively.
STEPS TO REPRODUCE
1. System Settings
2. Shortcuts
3. Add
4. Press key that send KEY_PROG2
OBSERVED RESULT
No change
EXPECTED RESULT
KEY_PROG2 is bound.
SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
ADDITIONAL INFORMATION
I checked xkb and qt6base and they both have the definition mapped to Launch2,
and that looks proper at first glance.
Mapping the same hw key to PROG4 works, so it's just PROG2.
evtest properly reports the key as follows:
Event: time 1745414363.951980, type 4 (EV_MSC), code 4 (MSC_SCAN), value 4c
Event: time 1745414363.951980, type 1 (EV_KEY), code 149 (KEY_PROG2), value 1
Event: time 1745414363.951980, -------------- SYN_REPORT ------------
Event: time 1745414363.952009, type 1 (EV_KEY), code 149 (KEY_PROG2), value 0
Event: time 1745414363.952009, -------------- SYN_REPORT ------------
--
You are receiving this mail because:
You are watching all bug changes.
