Bug 1954522 - Microphone shown in pavucontrol, not in gnome audio settings
Summary: Microphone shown in pavucontrol, not in gnome audio settings
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 34
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-28 10:29 UTC by Giuseppe Bonocore
Modified: 2022-06-08 06:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-08 06:32:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
mic working in pavucontrol, not in gnome settings (615.25 KB, image/png)
2021-04-28 10:29 UTC, Giuseppe Bonocore
no flags Details

Description Giuseppe Bonocore 2021-04-28 10:29:00 UTC
Created attachment 1776496 [details]
mic working in pavucontrol, not in gnome settings

Description of problem:

External usb microphone (Texas Instruments PCM2902) not seen in audio settings (but seen and working in pavucontrol / browser), on a lenovo thinkpad t490s



Version-Release number of selected component (if applicable):


How reproducible:

Always reproducible


Steps to Reproduce:
1.Install fedora 34
2. Attach behringer u-phoria um2 usb external card (and microphone)


Actual results:

PCM2902 working and selectable from gnome audio applet as output, but not as input (microphone)

Expected results:

Card working both as input and output (as it was in f33)


Additional info:

The input microphone is working correctly both under pavucontrol and in firefox media (e.g. google meet). Is just not controllable from the gnome audio settings

Comment 1 Giuseppe Bonocore 2021-04-29 09:07:31 UTC
Apparently, commenting the line:

ATTRS{idVendor}=="08bb", ATTRS{idProduct}=="2902", ENV{ACP_PROFILE_SET}="behringer-umc22.conf"

in:

/lib/udev/rules.d/90-pipewire-alsa.rules

did the trick:

I can now see and control also the input of my behringer everywhere (including the gnome settings / audio applet).

It may be a wrong behringer-umc22.conf ?

Anyway, before the device was shown in pavucontrol by with no "port" available (even if it was working correctly), now everything seems to be ok

Hope this help!

Comment 2 Giuseppe Bonocore 2021-05-11 11:09:42 UTC
Still true after a couple of updates. The rule in 90-pipewire-alsa.rules get uncommented after every system update, but commenting it again I am able to solve the issue

Comment 3 Fedora Update System 2021-06-03 10:34:36 UTC
FEDORA-2021-4bd6fdd9d3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4bd6fdd9d3

Comment 4 Fedora Update System 2021-06-04 01:18:16 UTC
FEDORA-2021-4bd6fdd9d3 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4bd6fdd9d3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4bd6fdd9d3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Ben Cotton 2022-05-12 16:59:01 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Ben Cotton 2022-06-08 06:32:55 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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.

Thank you for reporting this bug and we are sorry it could not be fixed.


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