On Fri Jan 9, 2026 at 1:55 AM CET, Christopher Cooper wrote:
> Seems likely the same as
> https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8948.
>
> Christopher

Thank you. Yes, reading through that thread and also the subsequent
reports linked there, it appears to be a bug in wireplumber 0.5.13 in
pipewire 1.5.84. It has been reported upstream[1].

There is a workaround available (apart from downgrading wireplumber to
0.5.12):

    $ wpctl settings bluetooth.autoswitch-to-headset-profile false

However that messes things a bit up with autoswitching across devices
and downgrading seems to require downgrading all of pipewire as well, so
for the time being I'll be careful not to turn the headset off from
hardware.

[1]: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5053

-- 
Ariadna Vigo
https://ariadnavigo.xyz
gpg 0xC948873069856D6D

Attachment: signature.asc
Description: PGP signature

Reply via email to