SUMMARY On X11 when binding 2 functions to a key in xkeyboard-config like this for example: `key <MUTE> { [ XF86AudioMute, XF86TouchpadToggle ], type[group1] = "PC_SUPER_LEVEL2"};` xev and systemsettings->shortcuts both correctly see `Meta + TouchpadToggle` when pressing `Meta + Mute`. However plasma still reacts to the XF86AudioMute keypress and not to the XF86TouchpadToggle one. STEPS TO REPRODUCE 1. Edit /usr/share/X11/xkb/symbols/inet to have `key <MUTE> { [ XF86AudioMute, XF86TouchpadToggle ], type[group1] = "PC_SUPER_LEVEL2"};` instead of `key <MUTE> { [ XF86AudioMute ] };` and reboot to apply the settings change. 2. Bind Meta + TouchpadToggle to touchpad toggle using systemsettings -> shortcuts 3. Press Meta + Mute OBSERVED RESULT Audio is muted EXPECTED RESULT Touchpad is disabled SOFTWARE/OS VERSIONS Linux: 6.14 KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION The example above is a constructed example to more easily reproduce a bug I came across in this more complicate real world example (it would require a kernel patch, a special notebook, and a new xkeyboard-config type defintion): https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/816
A possible workaround for the realworld problem the caused me to stumble over this bug would be to add yet another default binding to touchpad toggle: "Control + Meta + F24".
A gentle bump. Does anybody have an idea where to look to fix this?
bump again It is mainly relevant for this: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/merge_requests/866 hope that gets included, but still need the fix on this side
(In reply to Werner Sembach [TUXEDO] from comment #3) > bump again > > It is mainly relevant for this: > https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/ > merge_requests/866 > > hope that gets included, but still need the fix on this side small update: the xkb patch is now merged