Package: wireplumber Version: 0.5.13-1 On Mon, 12 Jan 2026 15:14:23 +0100 =?UTF-8?B?RHlsYW4gQcOvc3Np?= <[email protected]> wrote: > Hi, > > Le lun. 12 janv. 2026 à 14:13, Alban Browaeys <[email protected]> a écrit : > > > > Dear Maintainer, > > Well I was wrong, I reverted to pipewire/libspa 1.4.9-1+b1 and > > gsd-media-keys and gnome-shell still crash when I have audio input > > source as the bluetooth one. > > Even after a reboot. > > > > I am puzzled. > > > > Can you try to downgrade to wireplumber 0.5.12? Or to run:
indeed with the downgrade of libwireplumber-0.5-0_0.5.12-3_amd64.deb and wireplumber_0.5.12-3_amd64.deb from snapshot.debian.org and restarting wireplumber user session, the issue is fixed. I can switch input to bluetooth HSP/HFP back and forth in gnome-control-center without issue with pipewire 1.4.9-1+b1 from forky, 1.4.10-1 from unstable and 1.5.84-1+b2 from rc-buggy. But note that rc-buggy pipewire 1.5.84-1+b2 does not work for bluetooth (but produces no crashes, only a hang for a few seconds). Be it audio out or in A2DP or HSP/HFP whatever the codec selected. While for pipewire 1.4.9 and 1.4.10 both works (even if there are some minor issues, which were the cause of my trying rc-buggy pipewire but I can live with these for now). > > wpctl settings bluetooth.autoswitch-to-headset-profile false > Well at times the profile felt back to A2DP and no HFP for input, then no crash until I switched to HFP. Not tried but likely would have allowed me to start gnome-shell until I attempted to switch back to HFP. > Best regards, > Dylan Thanks a lot, I did not though of wireplumber as a culprit. Alban
