Created attachment 942035 [details] alsa-info Description of problem: This is a revision of Bug 982786. The internal microphone on my notebook requires the boost be set for it to be usable. It can be set using alsa-mixer, but PA routinely resets it to 0 (e.g. when starting, or if I change the input device away from internal mic to analogue input and back again). Version-Release number of selected component (if applicable): pulseaudio-5.0-10.fc21.x86_64 alsa-lib-1.0.28-2.fc21.x86_64 How reproducible: Always. 1. Open GNOME Sound Settings, go to Input tab. 2. Select the Internal Microphone as the input. 3. Run alsamixer -c0 to observe settings. Ensure that mic boost is set > 0 so that sounds register on the Sound Settings meter. 4. Back in Sound Settings, select Analog Input as input, then the microphone again. Actual results: Mic boost has dropped to 0. No audio recorded from internal microphone. Expected results: Mic boost setting preserved, or kept to a sensible level. Additional info: The output of alsa-info is attached. Please note at the time it was taken, an USB audio output device was attached as well. The microphone I want to use is on the notebook's built-in Intel HDA device.
Still present in pulseaudio-5.0-25.fc21.x86_64
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still present with: kernel-4.2.5-300.fc23.x86_64 alsa-lib-1.0.29-2.fc23.x86_64 pulseaudio-7.1-1.fc23.x86_64
Still present with: kernel-4.5.4-300.fc24.x86_64 pulseaudio-8.0-6.fc24.x86_64 alsa-lib-1.1.1-1.fc24.x86_64
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.