Bug 1817100 - Is it possible PulseAudio could lose "duplex" preference, confusing users wrt. microphone availability?
Summary: Is it possible PulseAudio could lose "duplex" preference, confusing users wrt...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-25 15:03 UTC by Jan Pokorný [poki]
Modified: 2020-09-14 11:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Jan Pokorný [poki] 2020-03-25 15:03:05 UTC
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]

Comment 1 Ben Cotton 2020-08-11 13:15:12 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 2 Pasi Karkkainen 2020-09-14 11:40:23 UTC
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).


Note You need to log in before you can comment on or make changes to this bug.