Hello, I've run into the problem that pavucontrol was not showing me the internal microphone in Input Devices tab. To no avail. There was a heureka point: after a tweak of "Internal Mic Boost" in alsamixer, I was able to record myself and let it reproduce for confirmation just fine (arecord, aplay). Then, there was another, when I figured out that in Configuration tab in pavucontrol, I had "Analog Stereo Output" selected. When flipped to "Analog Stereo Duplex", everything under Input Devices started as expected. This may perhaps be a question on pavucontrol rather than here, but is it possible that something had changed "Analog Stereo Duplex" to "Analog Stereo Output" and that something wasn't me? I mean, information lost on upgrade of pulseaudio or something like this? If unlikely, still, there would be this RFE from my side on pavucontrol (let's move this bug over there, then): Please, when Input Devices tab is empty AND there is not a duplex mode selected in Configuration tab, show a hint on the former that the users can help themselves going to the latter and selecting a duplex option should they expect a microphone settings available. $ rpm -q pavucontrol alsa-utils; uname -r > pavucontrol-4.0-3.fc32.x86_64 > alsa-utils-1.2.2-1.fc33.x86_64 > 5.6.0-0.rc6.git2.1.fc33.x86_64 snippet from alsa-info.sh: > !!Soundcards recognised by ALSA > !!----------------------------- > > 0 [PCH ]: HDA-Intel - HDA Intel PCH > HDA Intel PCH at 0xf2240000 irq 134 > > > !!PCI Soundcards installed in the system > !!-------------------------------------- > > 00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller [8086:a170] (rev 31) > Subsystem: Lenovo Device [17aa:5050]
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
Recently I've seen lots of problems with the pulseaudio profiles getting messed up on their own, exactly like you described, so the end result is microphone not available.. and sometimes one needs to restart pulseaudio and/or re-plug the audio device (usb-headset in my case) before the correct "duplex" profile can be chosen again. I'm on Fedora 32 atm (but f32 has similar pulseaudio version than F33).
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.