Hello Hui, or anyone else affected, Accepted alsa-utils into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- utils/1.2.2-1ubuntu2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1899745 Title: [SRU] alsa-utils: let alsactl support _boot section defined in ucm Status in HWE Next: New Status in alsa-utils package in Ubuntu: Fix Released Status in alsa-utils source package in Focal: Fix Committed Bug description: This patchset was backported from mainline alsa-utils 1.2.3, and groovy already integrated alsa-utils 1.2.3, there is no need to SRU this patchset to groovy, so only for focal. [Impact] We enabled 2 Dell soundwire audio machines, these machines depend on ucm to make the audio work, and in the ucm, the _boot section defined some amixers values for the 1st booting, these amixer values should be set to audio driver at the 1st booting, otherwise the whole audio doesn't work. [Fix] Backport some patches from mainline v1.2.3, these patches make the alsactl support _boot section in the ucm, then the systemd will call alsactl init after booting, the alsactl init will setting all amixers defined in the _boot section of ucm. [Test Case] On the Dell soundwire audio machines, After booting up, run 'amixer contents | less' to check all amixer values defined in the _boot section of ucm, all values read from driver are same as the ones in the ucm, test speaker/microphone/headset, all work well. [Regression Risk] This could introduce failure on runing 'alsactl init' for some machines, then the amixers will not be initialized correctly, users will experience all audio can't work like speaker doesn't output sound or microphone can't record sound. But this regression possibility is very low, since We have tested it both on soundwire machines and non-soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
