On Fri, Sep 10, 2021 at 12:37 PM Vincent Lefevre <[email protected]> wrote: > I could eventually solve the problem, which was apparently caused by > some other Bluetooth audio device. Some details below... > > [skip] > > What I did first is to upgrade again to pulseaudio 15.0+dfsg1-2, then > reboot. With my settings, I automatically connect to 7C:96:D2:4E:98:41 > after logging in. As before, I could then connect to the headset with > > bluetoothctl connect 38:18:4C:4B:AC:93 > > which succeeded, but the headset wasn't recognized by PulseAudio 15. > I had to disconnect from both devices with 2 "bluetoothctl disconnect" > commands, then connect to the headset *alone* so that it could get > recognized by PulseAudio 15.
This looks very much like an issue with bluez side caching of available device profiles, this was being worked on in subsequent bluez releases. _______________________________________________ pkg-pulseaudio-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pulseaudio-devel
