Hello Joao, or anyone else affected, Accepted alsa-lib into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.11-1ubuntu0.1 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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/2111271 Title: Add HDA-Intel config alias for snd_hda_acpi to enable discovery of ACPI-advertised devices Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Noble: Fix Committed Status in alsa-lib source package in Oracular: Won't Fix Status in alsa-lib source package in Plucky: Fix Committed Status in alsa-lib source package in Questing: Fix Released Bug description: SRU Justification: [ Impact ] * This is a hardware enablement SRU. * It adds an alias to alsa-lib to handle the enw hardware correctly. [ Fix ] * Adding `hda-acpi cards.HDA-Intel` to the conf/cards/aliases list. [ Test Plan ] * Install the newest libasound package from proposed on a N1X device running Noble * On the same device, install the latest -nvidia kernel from the kernel team PPA: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/nvidia/+packages?field.name_filter=nvidia-6.11&field.series_filter=noble * On the same device, verify that audio works with simple use of `aplay <file.wav>`. * Install the newest libasound package from proposed on a generic device * Check for regression with a simple use of `aplay <file.wav>` [ Where problems could occur ] * The new name could be wrong, and the hardware would not get enabled. That would require a patch upstream, and then a backport again. Assuming NVIDIA (who carried the fix upstream) did not make that mistake, since it got merged to main. Original description: There is a new audio driver upstream: https://lore.kernel.org/all/aCXswg1gr6cufyzp@ddadap- lakeline.nvidia.com/. Once the support for this driver lands on the Kernel, alsa-lib needs to be changed to add a new alias: https://lore.kernel.org/alsa-devel/aCXs810qs_pvuOtx@ddadap- lakeline.nvidia.com/ Upstream commit: https://git.alsa-project.org/?p=alsa- lib.git;a=patch;h=07ec2ad34c42dba8656d3f543164f360f481c52e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/2111271/+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
