Between this and 2103967 the hwdb approach the approach with the most limited range of problems, targeting only specific hardware, at the cost of possibly needing further updates when *new* hardware exists.
Hm. But by my understanding of the input stack, *this* will result in both Wayland and Xorg sessions seeing the extra key as F20, which is a change of behaviour for Wayland sessions which would currently see KEY_MICMUTE and which users could have configured bindings for? So perhaps 2103967 is the conservative approach - it only applies to Xorg, where no-one can be using KEY_MICMUTE as it has a keycode greater than (255 - 8), and I *think* anyone who has remapped it with a hwdb entry will be unaffected by the x-x-i-libinput patch (as it will already have been remapped before hitting the codepath in the patch). Does that sound right to everyone else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2105957 Title: [SRU] Add micmute key for Dell Pro Max series To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2105957/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
