Arch Linux

sc6ut

Member

Registered: 2021-08-18

Posts: 26

[SOLVED] Pipewire: USB hotplug detection

My USB headphones are not being detected by pipewire when it's being plugged, although the mic from it is being detected good. The restart of pipewire services helps (systemctl --user restart pipewire pipewire-pulse pipewire-media-session), but may be someone know is it possible to fix that issue?

Last edited by sc6ut (2021-08-27 09:03:22)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,310

Re: [SOLVED] Pipewire: USB hotplug detection

Is it not detected or are audio sources simply not automatically switched and you could do so via pavucontrol/pactl ?

If the latter and you want that to happen you need to load module-switch-on-connect which you can do via pipewire's session manager: https://gitlab.freedesktop.org/pipewire … figuration

Last edited by V1del (2021-08-26 09:37:08)

sc6ut

Member

Registered: 2021-08-18

Posts: 26

Re: [SOLVED] Pipewire: USB hotplug detection

Is it not detected or are audio sources simply not automatically switched and you could do so via pavucontrol/pactl ?

The output is not detected, as I already wrote, and the input (the headphones' mic) is detected, but it is not switched automatically.

Last edited by sc6ut (2021-08-26 09:41:31)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,310

Re: [SOLVED] Pipewire: USB hotplug detection

Since you didn't include technical information that would make this clear it's better to ask whether this is a matter of (mis)-understanding than assume it to be a bug.

FWIW: https://gitlab.freedesktop.org/pipewire … ssues/1534 and https://bugs.archlinux.org/task/71765 - to which I've now added a comment that the referenced commit may be backported

Edit: Should be fixed in the new pipewire release, if we can trust the changelog.

Last edited by V1del (2021-08-26 20:01:07)

sc6ut

Member

Registered: 2021-08-18

Posts: 26

Re: [SOLVED] Pipewire: USB hotplug detection

Edit: Should be fixed in the new pipewire release, if we can trust the changelog.

True, it was fixed with last release. So solved..