thank you for the update. However, I've tried to connect my headset after the update of the corresponding packages to the specified version and the headset entered disconnection/reconnection loop, until I tried to open Bluetooth Settings and it crashed the shell again, bringing me to login screen. According Gemini, it was a corrupt state of Pipewire and after clearing it, it seems to work. FYI, some commands to execute if needed: rfkill block bluetooth systemctl --user stop wireplumber pipewire pipewire-pulse rm -rf ~/.local/state/wireplumber systemctl --user start wireplumber pipewire pipewire-pulse wpctl settings bluetooth.autoswitch-to-headset-profile false rfkill unblock bluetooth
So this deactivates the autoswitch, however, previously the manual switch would crash the shell too, so now it seems to work. In any case, there was a segfault of both wireplumber and pipewire at 08:06 UTC, when I did that, so I'm attaching journalctl -b 0 logs ** Attachment added: "journalctl_bluetooth.txt" https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2137545/+attachment/5939229/+files/journalctl_bluetooth.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2137545 Title: Wireplumber 0.5.13 causing assert in gvc when Bluetooth headset device is connected To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2137545/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
