Bug 2096193 - USB headset cannot select rate
Summary: USB headset cannot select rate
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 36
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-13 09:12 UTC by John Clark
Modified: 2022-06-23 13:29 UTC (History)
7 users (show)

Fixed In Version: pipewire-0.3.52-4.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-23 08:01:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description John Clark 2022-06-13 09:12:51 UTC
Description of problem:
Since the upgrade to 0.3.52 I am unable to use my headset during Citrix HDX. Downgrading fixes it.

The logs reveal this:
```
Jun 14 06:46:09 fedora pipewire[1833]: spa.alsa: front:0: Rate doesn't match (requested 44100Hz, got 48000Hz)
Jun 14 06:46:09 fedora pipewire[1833]: spa.alsa: front:0: Rate doesn't match (requested 44100Hz, got 48000Hz)
Jun 14 06:46:09 fedora pipewire[1833]: spa.alsa: front:0: Rate doesn't match (requested 44100Hz, got 48000Hz)
Jun 14 06:46:09 fedora pipewire[1833]: spa.alsa: front:0: Rate doesn't match (requested 44100Hz, got 48000Hz)
Jun 14 06:46:09 fedora pipewire[1833]: pw.link: 0x564d9b486b90: one of the nodes is in error out:suspended in:error
Jun 14 06:46:09 fedora pipewire[1833]: pw.link: 0x564d9b4881a0: one of the nodes is in error out:suspended in:error
Jun 14 06:46:13 fedora pipewire[1833]: spa.alsa: front:0: Rate doesn't match (requested 44100Hz, got 48000Hz)
Jun 14 06:46:13 fedora pipewire[1833]: pw.node: (alsa_output.usb-Sennheiser_Sennheiser_SC_1x5_USB_A002460204909793-00.analog-stereo-52) suspended -> error (Start error: Invalid argument)
Jun 14 06:46:13 fedora pipewire[1833]: pw.link: 0x564d9b4d8cd0: one of the nodes is in error out:running in:error
Jun 14 06:46:14 fedora pipewire[1833]: spa.alsa: front:0: Rate doesn't match (requested 44100Hz, got 48000Hz)

```

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

How reproducible:
100%

Steps to Reproduce:
1. Update to 0.3.52
2. Attempt to place a Skype call using Citrix HDX

Actual results:
Skype hangs attempting to connect to the audio

Expected results:
The connection succeeds

Additional info:
Downgrading pipewire fixes the issue. This has also been an issue in previous pipewire versions.

Comment 1 Wim Taymans 2022-06-14 08:21:53 UTC
It's really a driver issue. It reported support for 44100 Hz but then when we tried to configure it, it refuses.

This bug is triggered by the PipeWire update because we now allow switching to 44100Hz on the fly.

As a workaround you can place a 10-lock-samplerates.conf file in ~/.config/pipewire/pipewire.conf.d/ with the following contents:

context.properties = {
    default.clock.allowed-rates = [ 48000 ]
}

It should then not attempt to use 44100Hz anymore.

Comment 2 Eric Lavarde 2022-06-22 16:49:58 UTC
I have the same issue with a Plantronics C720 (also USB device), the hang happens with Thunderbird notifying me (I think), and also when starting a Google Meet meeting in Chromium.

I'll try the workaround and let you know if it helps, but it could potentially impact quite a lot of people. Shouldn't pipewire simply be more lenient, and accept whatever it gets instead of stalling?

Comment 4 Brant Evans 2022-06-22 17:19:06 UTC
I think I'm hitting the same issue using a Logitech Brio Webcam microphone (connected via USB) when using Microsoft Teams. Teams is not able to connect to the microphone. I haven't experienced any hangs, but Teams reports an error connecting to the mic.

I'll also try the work around to see if it helps.

Comment 5 Kevin P. Fleming 2022-06-22 17:35:13 UTC
I'm having this issue with a Plantronics Savi W710 (also USB-connected). I've put the configuration file in place and will restart the system to see if the problem disappears.

Comment 6 Brant Evans 2022-06-22 17:52:16 UTC
I added the workaround and now the microphone is again working with MS Teams and there are no errors in the logs.

Comment 7 John Clark 2022-06-22 19:13:59 UTC
The workaround works for me too, thanks.

P.s. I'm also using a Plantronics headset.

Comment 8 Wim Taymans 2022-06-23 07:14:09 UTC
> Shouldn't pipewire simply be more lenient, and accept whatever it gets instead of stalling?

Ideally yes, I would have to investigate how that can work...

Comment 9 Fedora Update System 2022-06-23 07:59:20 UTC
FEDORA-2022-f4828b651e has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f4828b651e

Comment 10 Fedora Update System 2022-06-23 08:01:51 UTC
FEDORA-2022-f4828b651e has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Wim Taymans 2022-06-23 08:32:37 UTC
> > Shouldn't pipewire simply be more lenient, and accept whatever it gets instead of stalling?
> Ideally yes, I would have to investigate how that can work...

Fixed upstream now: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/0f62d3442cba151db1a04a068ce6f3211823a883

The pending fedora update only has the removal of the 44100Hz rate, though.

Comment 12 Eric Lavarde 2022-06-23 13:29:18 UTC
After almost a day of work with the workaround, it seems to solve the issue also for me. Thanks a lot!


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