Re: Re: Re: Can't connect bluetooth headset after resent update (testing)

[Олександр Скоропад]

> Checked but no luck. I can pair headset but can't use it(

Another thread here reported following
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997862=no=no=norelated
> to bug #997862 which seemed to work for me, that is,installing a package
> libspa-0.2-bluetooth.and I found on the PA devel mailing listBug#993011:
> pulseaudio-module-bluetooth: no longer detects bluetooth headphones
> do you have libspa-0.2-bluetooth installed?
>

This solution worked for me! Thanks a lot

Re: Re: Can't connect bluetooth headset after resent update (testing)

[Олександр Скоропад]

Checked but no luck. I can pair headset but can't use it(

Re: Can't connect bluetooth headset after resent update (testing)

[deloptes]

Олександр Скоропад wrote:

> Unfortunately not my case, because libpulse-mainloop-glib0 already
> installed

try 

backup and deleting
~/.pulse
/var/lib/bluetooth/
reboot
pair

regards

-- 
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

Re: Can't connect bluetooth headset after resent update (testing)

[Олександр Скоропад]

Unfortunately not my case, because libpulse-mainloop-glib0 already installed

Re: Can't connect bluetooth headset after resent update (testing)

[deloptes]

Олександр Скоропад wrote:

> Nov 1 16:09:10 Skoropad bluetoothd[1204]:
> src/service.c:btd_service_connect() a2dp-sink profile connect failed for
> 00:16:94:42:30:F4: Protocol not available I've found that there were
> similar error with previous versions of pipewire and apt history shows
> that there was pipewire update couple of days before issue (I don't use
> headset everyday), so maybe it's related to this isue

I had this recently too. One package was missing. I think it was 
libpulse-mainloop-glib0:amd64

-- 
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

Can't connect bluetooth headset after resent update (testing)

[Олександр Скоропад]

In bluetooth log there is only one line:

Nov 1 16:09:10 Skoropad bluetoothd[1204]: src/service.c:btd_service_connect() 
a2dp-sink profile connect failed for 00:16:94:42:30:F4: Protocol not available
I've found that there were similar error with previous versions of pipewire and 
apt history shows that there was pipewire update couple of days before issue (I 
don't use headset everyday), so maybe it's related to this isue