[Bug 1899857] Re: [SRU] alsa-lib: support the enum value settings both in "" and in ''

[Hui Wang]

This is the debdiff for focal.

thx.


** Patch added: "alsa-lib_1.2.2-2.1ubuntu3.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1899857/+attachment/5422370/+files/alsa-lib_1.2.2-2.1ubuntu3.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1899857

Title:
  [SRU] alsa-lib: support the enum value settings both in "" and in ''

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Recently the ucm added some amixer settings, like this one:
  cset "name='rt711 ADC 23 Mux' 'MIC2'"
  This setting is needed for Dell soundwire audio machines, and only
  this setting is set correctly, the headset-mic could work. And we
  already backported this ucm to focal. But the alsa-lib ctl parse
  doesn't support the enum value in the '' yet, so this amixer setting
  can't be set correctly under current focal and groovy, we need to
  backport a patch from alsa-lib master branch.

  [Fix]
  Backport a patch from upstream, this patch is not in the groovy
  yet (not in the alsa-lib v1.2.3.2), so both groovy and focal need this
  patch.

  [Test Case]
  On the Dell soundwire audio machine, run alsactl init, then check if
  the amixer "rt711 ADC 23 Mux" is set to "MIC2" or not, if it is set
  correctly, it means the alsalib enum ctl parse support both "" and ''
  now.

  
  [Regression Risk]
  This could introduce failure on setting enum amixer settings, users
  will experience the failure of audio device like the speaker can't output
  sound, the mic can't record sound. But this possibility is very low since
  we have tested this SRU on many LENOVO and Dell machines (with and without
  soundwire audio), all worked as fine as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1899857/+subscriptions