After update wireplumber to 0.4.90-1.fc41 version only headset mic is working when I connect bluetooth headset. But I don't want use headset mic because I prefer use separate hi-end wireless microphone system. Temporary solution downgrade to last good version. It is wireplumber 0.4.81-1.fc40. > koji download-build wireplumber-0.4.81-1.fc40 --arch="i686" --arch="x86_64" --arch="noarch" --debuginfo # dnf5 downgrade wireplumber --refresh > systemctl restart wireplumber --user Reproducible: Always
Created attachment 2021399 [details] gnome control center / sound
Proposed as a Blocker for 40-final by Fedora user mikhail using the blocker tracking app because: I think nowadays working mic very important modern workstation. Because I have everyday working meeting and mic quality has big matter. And yes it time prefer wireless solutions. And very annoying when you use Bluetooth headset and select super duper mic and colleagues didn't hear you. And you can't understand what happens, because in gnome control center at the sound page the monitoring is lying because you see working input level meter, but no one application get sound.
Can you try with 0.5.0 and see if it's fixed? it is now in Rawhide and pending update for F40...
Discussed during the 2024-03-18 blocker review meeting: [1] The decision to classify this bug wasn't made: "The affected wireplumber is not stable for F40 yet, and 0.5.0 has come out in the mean time. let's punt on this one and ask the reporter to test with 0.5.0. if 0.5.0 is broken, and it gets pushed stable for F40, then we can make a decision on it..." [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-03-18/f40-blocker-review.2024-03-18-16.01.log.html
(In reply to Adam Williamson from comment #3) > Can you try with 0.5.0 and see if it's fixed? it is now in Rawhide and > pending update for F40... # rpm -qa | grep wireplumber | sort wireplumber-0.5.0-1.fc41.x86_64 wireplumber-libs-0.5.0-1.fc41.x86_64 I am just checked wireplumber-0.5.0 and confirm that the problem not fixed yet.
Can you also report this upstream to https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues , if you didn't already? It's probably more likely to reach the attention of the developers there. Thanks!
This is very likely not a pipewire or wireplumber problem but a bluetooth (bluez) problem. The usual things to try: 1. try to repair the headset 2. clear the bluez cache: Delete all files and directories under /var/lib/bluetooth/ and systemctl restart bluetooth. This forgets all devices and you need to pair devices again. If none of this works, make a new pipewire issue.
(In reply to Wim Taymans from comment #7) > This is very likely not a pipewire or wireplumber problem but a bluetooth > (bluez) problem. > > The usual things to try: > > 1. try to repair the headset > 2. clear the bluez cache: Delete all files and directories under > /var/lib/bluetooth/ and systemctl restart bluetooth. > This forgets all devices and you need to pair devices again. > > If none of this works, make a new pipewire issue. I am just checked new wireplumber 0.5.0 after re-pairing all bluetooth devices and the issue reproduced again. Demonstration: https://youtu.be/45ogCBSesA8
Check with pavucontrol that no stream or source is muted?
(In reply to Wim Taymans from comment #9) > Check with pavucontrol that no stream or source is muted? In pavucontrol I see that headset mic is selected. And if I try change it manually to another mic it immediately reset to headset mic automatically. Demonstration: https://youtu.be/TX1kHF0BsQA
Looks like upstream thinks https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/620 fixes this. I'll do a scratch build for you to test shortly, Mikhail.
Can you please test https://koji.fedoraproject.org/koji/taskinfo?taskID=115420757 , Mikhail? Thanks!
Discussed at 2024-03-25 blocker review meeting: https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-03-25/f40-blocker-review.2024-03-25-16.00.html . Rejected on the grounds that this is too tied to hardware specifics to really block the release on, we typically would only block the release for a sound issue if it affected all hardware or a huge swathe of it.
(In reply to Adam Williamson from comment #12) > Can you please test > https://koji.fedoraproject.org/koji/taskinfo?taskID=115420757 , Mikhail? > Thanks! I confirm that patch https://gitlab.freedesktop.org/pipewire/wireplumber/-/merge_requests/620 fixed this issue.
Great, thanks. I'll send an official build.
FEDORA-2024-194ff57394 (wireplumber-0.5.0-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-194ff57394
FEDORA-2024-6b4f717fcb (wireplumber-0.5.0-2.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-6b4f717fcb
FEDORA-2024-194ff57394 (wireplumber-0.5.0-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-6b4f717fcb has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6b4f717fcb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6b4f717fcb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-6b4f717fcb (wireplumber-0.5.0-2.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.