[Bug 2105957] Re: [SRU] Add micmute key for Dell Pro Max series

[Chris Halse Rogers]

>> 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?

> That is the convention used in the version of systemd hwdb under noble
and oracular. The hwdb used in plucky does not convert micmute key to
f20 there.

And the x-x-i-libinput patch won't result in a change of behaviour for
systems that already have a hwdb entry (as it's already remapped to
F20), and will mean we won't need to make any more updates to the hwdb
for this issue.

I therefore think 2103967 is the safer option, and what we should
pursue.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd-hwe in Ubuntu.
Matching subscriptions: systemd-hwe
https://bugs.launchpad.net/bugs/2105957

Title:
  [SRU] Add micmute key for Dell Pro Max series

Status in OEM Priority Project:
  New
Status in systemd-hwe package in Ubuntu:
  Invalid
Status in systemd-hwe source package in Noble:
  Confirmed
Status in systemd-hwe source package in Oracular:
  Confirmed

Bug description:
  [ Impact ]

   * This patch adds hwdb entries to map mic mute keycode to F20, so
  that the key is usable in Xorg.

  [ Test Plan ]

   * On targeted unit, under Xorg, test that mic mute does not work

   * Update the package to -proposed and restart desktop, test the same
  key, the mic mute key should work to mute the microphone.

  [ Where problems could occur ]

   * Since the key is mapped to F20 (by convention in xkeyboard-config),
  if user redefine F20 for other purposes, it might not work as
  intended.

  [ Other Info ]

   * Do not update for plucky. In plucky, the keycode translation is
  done in xserver-xorg-input-libinput (see Bug #2103967), and wayland
  can take the micmute keycode as is.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2105957/+subscriptions