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

[Yao Wei]

It is not needed for plucky as we have tested that the changes in
xserver-xorg-input-libinput which is included in plucky fixed this
issue.

The main reason for mapping micmute key to f20 is thst Xorg does not
take key code > 255 (in wayland, usually it takes the key code as-is
from libinput) but mic mute key is at 256 after offsetting by 8 from
kernel key code. In noble and oracular we use hwdb to workaround the
issue.  From plucky, the patches initiated from systemd developers
decided not to include such hacks, and the responsibility is pushed to
Xorg input modules.

I've posted the story in Bug #2103967

-- 
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:
  Incomplete
Status in systemd-hwe source package in Noble:
  New
Status in systemd-hwe source package in Oracular:
  New

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