[Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
fossfreedom
1897934 at bugs.launchpad.net
Thu Oct 22 15:08:12 UTC 2020
I can confirm that sound is no longer muted for the ISO and is not muted on
installation.
So thanks and congrats!
On Thu, 22 Oct 2020, 14:30 Launchpad Bug Tracker, <
1897934 at bugs.launchpad.net> wrote:
> This bug was fixed in the package alsa-lib - 1.2.3.2-1ubuntu3
>
> ---------------
> alsa-lib (1.2.3.2-1ubuntu3) groovy; urgency=medium
>
> * d/p/0001-ucm-add-a-check-for-the-empty-configuration.patch
> - Fix the failure on init the HDA-Intel sound card, because there
> is no init mixer values in the ucm, the alsa-lib should return
> error and then let alsautils init this sound card in the legacy
> HDA way. (LP: #1897934)
>
> -- Hui Wang <hui.wang at canonical.com> Thu, 22 Oct 2020 16:46:14 +0800
>
> ** Changed in: alsa-lib (Ubuntu Groovy)
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1897934
>
> Title:
> [SRU][Intel HDA] The initial sound level is set to zero (muted)
>
> Status in Release Notes for Ubuntu:
> New
> Status in alsa-lib package in Ubuntu:
> Fix Released
> Status in alsa-lib source package in Focal:
> Fix Committed
> Status in alsa-lib source package in Groovy:
> Fix Released
>
> Bug description:
> [Impact]
> Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
> results in the failure on setting the init mixer values for HDA sound
> card, and users experience the mute of audio after installing the
> 20.10.
>
> [Fix]
> Backport a patch from the latest alsa-lib (v1.2.3+)
>
> [Test]
> Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm
> /var/lib/alsa/*;
> sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
> muted.
>
> Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm
> /var/lib/alsa/*;
> sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
> not muted.
>
> [Regression Potential]
> This could make the ucm audio fail to initialize, but this possibility is
> very low, since this patch is from upstream, and I tested on a ucm based
> machine, the audio is good.
>
>
> On boot into the live session - or on first install the sound level is
> muted.
>
> I have to use GNOME Control Center - Sounds to change to an
> appropriate level. Once changed the level chosen is correctly
> retained between reboots.
>
> This appears to be a regression from 20.04 where the sound level was
> set to - I guess - 80% on the live-session/first install
>
> ProblemType: BugDistroRelease: Ubuntu 20.10
> Package: pulseaudio 1:13.99.1-1ubuntu11
> ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
> Uname: Linux 5.8.0-20-generic x86_64
> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
> ApportVersion: 2.20.11-0ubuntu48
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: ubuntu-budgie 5041 F.... pulseaudio
> CasperMD5CheckResult: pass
> CasperVersion: 1.452
> CurrentDesktop: Budgie:GNOME
> Date: Wed Sep 30 16:03:08 2020
> LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64
> (20200930)
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bashSourcePackage: pulseaudio
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 02/15/2016
> dmi.bios.release: 15.31
> dmi.bios.vendor: Insyde
> dmi.bios.version: F.1F
> dmi.board.asset.tag: Type2 - Board Asset Tag
> dmi.board.name: 80BF
> dmi.board.vendor: HP
> dmi.board.version: 95.16
> dmi.chassis.asset.tag: Chassis Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: HP
> dmi.chassis.version: Chassis Version
> dmi.ec.firmware.release: 95.22
> dmi.modalias:
> dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
> dmi.product.family: 103C_5335KV G=N L=CON B=HP
> dmi.product.name: HP Notebook
> dmi.product.sku: N9S73EA#ABU
> dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions
>
--
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/1897934
Title:
[SRU][Intel HDA] The initial sound level is set to zero (muted)
Status in Release Notes for Ubuntu:
New
Status in alsa-lib package in Ubuntu:
Fix Released
Status in alsa-lib source package in Focal:
Fix Committed
Status in alsa-lib source package in Groovy:
Fix Released
Bug description:
[Impact]
Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this
results in the failure on setting the init mixer values for HDA sound
card, and users experience the mute of audio after installing the 20.10.
[Fix]
Backport a patch from the latest alsa-lib (v1.2.3+)
[Test]
Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
muted.
Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*;
sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is
not muted.
[Regression Potential]
This could make the ucm audio fail to initialize, but this possibility is
very low, since this patch is from upstream, and I tested on a ucm based
machine, the audio is good.
On boot into the live session - or on first install the sound level is muted.
I have to use GNOME Control Center - Sounds to change to an
appropriate level. Once changed the level chosen is correctly
retained between reboots.
This appears to be a regression from 20.04 where the sound level was
set to - I guess - 80% on the live-session/first install
ProblemType: BugDistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.1-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: ubuntu-budgie 5041 F.... pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.452
CurrentDesktop: Budgie:GNOME
Date: Wed Sep 30 16:03:08 2020
LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bashSourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2016
dmi.bios.release: 15.31
dmi.bios.vendor: Insyde
dmi.bios.version: F.1F
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80BF
dmi.board.vendor: HP
dmi.board.version: 95.16
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 95.22
dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.sku: N9S73EA#ABU
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions
More information about the Ubuntu-sponsors
mailing list