Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
@ 2022-10-18  8:30 LinArcX
  2022-10-18 12:05 ` Duncaen
                   ` (24 more replies)
  0 siblings, 25 replies; 26+ messages in thread
From: LinArcX @ 2022-10-18  8:30 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]

New issue by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/40018

Description:
### Is this a new report?

Yes

### System Info

Void 5.19.16_1 x86_64 GenuineIntel notuptodate hold rFFF

### Package(s) Affected

bluez, dbus

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/bluez/bluez/issues/351

IT says that the issue is related to audio. And I installed every audio related package that exists in void for Bluetooth. Still got the same error.

### Expected behaviour

Whenever i wanted to connect to a Bluetooth device, I should do it without any issue.

### Actual behaviour

bluez can't connect to bluetooth devices.

### Steps to reproduce

1. install these packages first:
```
bluez
dbus
bluez
libspa-bluetooth
blueman
bluez-alsa-32bit
bluez-alsa
pipewire
pulseaudio
```

And enable service for:
```
pulseaudio
dbus
bluetoothd
```

Type: `bluetoothctl` and press ENTER. Then you can do lots of commands here. for example: `scan on`, `pair <DEV_ID>`, `truse <DEV_ID>`, etc..

All of them works without any problem. But I can't connect to any device:
```
Attempting to connect to <DEV_ID>
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
```

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
@ 2022-10-18 12:05 ` Duncaen
  2022-10-18 12:27 ` LinArcX
                   ` (23 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Duncaen @ 2022-10-18 12:05 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 213 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1282278766

Comment:
https://docs.voidlinux.org/config/media/pipewire.html#bluetooth-audio

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
  2022-10-18 12:05 ` Duncaen
@ 2022-10-18 12:27 ` LinArcX
  2022-10-18 13:06 ` paper42
                   ` (22 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: LinArcX @ 2022-10-18 12:27 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

New comment by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1282304073

Comment:
@Duncaen  Still get the same error.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
  2022-10-18 12:05 ` Duncaen
  2022-10-18 12:27 ` LinArcX
@ 2022-10-18 13:06 ` paper42
  2022-10-18 15:55 ` LinArcX
                   ` (21 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: paper42 @ 2022-10-18 13:06 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1282357472

Comment:
Installing all packages and enabling all services you can think of is not a good idea and it will only lead to hard to debug issues. If you want to use pulseaudio, don't install alsa packages, pipewire, don't enable the pulseaudio service and follow the handbook. If you want to use pipewire, Don't install pulseaudio, alsa packages, don't enable pulseaudio service and follow the handbook.

Installing 32bit packages also makes no sense.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (2 preceding siblings ...)
  2022-10-18 13:06 ` paper42
@ 2022-10-18 15:55 ` LinArcX
  2022-10-18 16:03 ` LinArcX
                   ` (20 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: LinArcX @ 2022-10-18 15:55 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 547 bytes --]

New comment by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1282624266

Comment:
@paper42 Thanks for your tip. As I was using the Alsa as my multimedia backend I removed all the packages, just keep:
```
dbus
bluez
bluez-alsa
```

And also disabled all the services and just re-enabled these ones:
```
dbus
bluetoothd
alsa
```
But still, get the same error!

Also, it's worth mentioning that I'm using seatd, not elogind. I don't know is it related to this issue or not.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (3 preceding siblings ...)
  2022-10-18 15:55 ` LinArcX
@ 2022-10-18 16:03 ` LinArcX
  2022-10-18 16:14 ` LinArcX
                   ` (19 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: LinArcX @ 2022-10-18 16:03 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

New comment by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1282624266

Comment:
@paper42 Thanks for your tip. As I was using the Alsa as my multimedia backend I removed all the packages, just keep:
```
dbus
bluez
bluez-alsa
```

And also disabled all the services and just re-enabled these ones:
```
dbus
bluetoothd
alsa
```
But still, get the same error!

Also, it's worth mentioning that I'm using seatd, not elogind. I don't know is it related to this issue or not.

I'm part of these groups, if it helps:
`linarcx : linarcx wheel floppy audio video cdrom optical kvm xbuilder tor bluetooth nixbld socklog _seatd`

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (4 preceding siblings ...)
  2022-10-18 16:03 ` LinArcX
@ 2022-10-18 16:14 ` LinArcX
  2022-10-18 16:27 ` LinArcX
                   ` (18 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: LinArcX @ 2022-10-18 16:14 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 758 bytes --]

New comment by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1282624266

Comment:
@paper42 Thanks for your tip. As I was using the Alsa as my multimedia backend I removed all the packages, just keep:
```
dbus
bluez
bluez-alsa
```

And also disabled all the services and just re-enabled these ones:
```
dbus
bluetoothd
alsa
```
But still, get the same error!

Also, it's worth mentioning that I'm using seatd, not elogind. I don't know is it related to this issue or not.

I'm part of these groups, if it helps:
`linarcx : linarcx wheel floppy audio video cdrom optical kvm xbuilder tor bluetooth nixbld socklog _seatd`

Edit: Seems it's a bug in bluez side. waiting for fix...

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (5 preceding siblings ...)
  2022-10-18 16:14 ` LinArcX
@ 2022-10-18 16:27 ` LinArcX
  2022-10-26 23:11 ` runrin
                   ` (17 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: LinArcX @ 2022-10-18 16:27 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

New comment by LinArcX on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1282624266

Comment:
@paper42 Thanks for your tip. As I was using the Alsa as my multimedia backend I removed all the packages, just keep:
```
dbus
bluez
bluez-alsa
```

And also disabled all the services and just re-enabled these ones:
```
dbus
bluetoothd
alsa
```
But still, get the same error!

Also, it's worth mentioning that I'm using seatd, not elogind. I don't know is it related to this issue or not.

I'm part of these groups, if it helps:
`linarcx : linarcx wheel floppy audio video cdrom optical kvm xbuilder tor bluetooth nixbld socklog _seatd`

Edit: Seems [it's a bug](https://github.com/bluez/bluez/issues/351#issuecomment-1282650185) in bluez side. waiting for fix...

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (6 preceding siblings ...)
  2022-10-18 16:27 ` LinArcX
@ 2022-10-26 23:11 ` runrin
  2022-12-10  8:20 ` eoli3n
                   ` (16 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: runrin @ 2022-10-26 23:11 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

New comment by runrin on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1292761848

Comment:
i have had some form of this issue (intermittently) when attempting to connect my headphones and bluetooth speakers for a while now. i'm on `Void 5.19.10_1 x86_64 AuthenticAMD`.

today i'm getting `Failed to connect: org.bluez.Error.Failed br-connection-unknown`.

i suspect this isn't an issue with the void package, and is more an issue with bluez itself. i've seen the same errors on my debian machines as well, along with other similarly inscrutable errors. my experience for years with bluetooth on multiple linux boxes has been that it only works correctly about 65% of the time.

sometimes it just doesn't feel like working, sometimes the service won't even restart with `sv restart` and i have to use `sv stop` instead.

the only thing that ever resolves this issue for me is rebooting my machine (and this only occasionally works, rebooting multiple times sometimes gets it to work again).

restarting pulseaudio and/or the bluetooth service have never worked for me.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (7 preceding siblings ...)
  2022-10-26 23:11 ` runrin
@ 2022-12-10  8:20 ` eoli3n
  2022-12-10  8:24 ` eoli3n
                   ` (15 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: eoli3n @ 2022-12-10  8:20 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 304 bytes --]

New comment by eoli3n on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1345183049

Comment:
I face this with:
- linux 5.15.74_1
- pipewire-0.3.61_1 
- bluez-5.65_1
- blueman-2.3.4_2
- libspa-bluetooth-0.3.61_1

scan/pair/trust ok
I can't connect

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (8 preceding siblings ...)
  2022-12-10  8:20 ` eoli3n
@ 2022-12-10  8:24 ` eoli3n
  2023-01-20 18:48 ` cybergsus
                   ` (14 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: eoli3n @ 2022-12-10  8:24 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 384 bytes --]

New comment by eoli3n on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1345183049

Comment:
I face this with:
- linux 5.15.74_1
- pipewire-0.3.61_1 
- bluez-5.65_1
- blueman-2.3.4_2
- libspa-bluetooth-0.3.61_1

scan/pair/trust ok
I can't connect

EDIT: i needed to restart pipewire (i guess, i rebooted), everythings work !

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (9 preceding siblings ...)
  2022-12-10  8:24 ` eoli3n
@ 2023-01-20 18:48 ` cybergsus
  2023-01-20 18:49 ` cybergsus
                   ` (13 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: cybergsus @ 2023-01-20 18:48 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 382 bytes --]

New comment by cybergsus on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1398798708

Comment:
Hey, I'm using PipeWire with its PulseAudio wrapper. In case this helps, I made sure bluetoothd started before pipewire, enabling bluetoothd as a service and starting `pipewire` and pipewire-pulse` from sway, once everything has started

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (10 preceding siblings ...)
  2023-01-20 18:48 ` cybergsus
@ 2023-01-20 18:49 ` cybergsus
  2023-01-20 20:34 ` paper42
                   ` (12 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: cybergsus @ 2023-01-20 18:49 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 383 bytes --]

New comment by cybergsus on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1398798708

Comment:
Hey, I'm using PipeWire with its PulseAudio wrapper. In case this helps, I made sure bluetoothd started before pipewire, enabling bluetoothd as a service and starting `pipewire` and `pipewire-pulse` from sway, once everything has started

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (11 preceding siblings ...)
  2023-01-20 18:49 ` cybergsus
@ 2023-01-20 20:34 ` paper42
  2023-01-24  9:38 ` cybergsus
                   ` (11 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: paper42 @ 2023-01-20 20:34 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1398904545

Comment:
> Hey, I'm using PipeWire with its PulseAudio wrapper. In case this helps, I made sure bluetoothd started before pipewire, enabling bluetoothd as a service and starting `pipewire` and `pipewire-pulse` from sway, once everything has started

I assume you have the same issue, right? Do you have libspa-bluetooth installed which was mentioned earlier in this thread? https://docs.voidlinux.org/config/media/pipewire.html#bluetooth-audio

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (12 preceding siblings ...)
  2023-01-20 20:34 ` paper42
@ 2023-01-24  9:38 ` cybergsus
  2023-01-24  9:39 ` cybergsus
                   ` (10 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: cybergsus @ 2023-01-24  9:38 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 417 bytes --]

New comment by cybergsus on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1401635178

Comment:

> I assume you have the same issue, right? Do you have libspa-bluetooth installed which was mentioned earlier in this thread? https://docs.voidlinux.org/config/media/pipewire.html#bluetooth-audio

Sure! I forgot to mention in my comment that what I did solved the issue.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (13 preceding siblings ...)
  2023-01-24  9:38 ` cybergsus
@ 2023-01-24  9:39 ` cybergsus
  2023-01-24  9:39 ` cybergsus
                   ` (9 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: cybergsus @ 2023-01-24  9:39 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 405 bytes --]

New comment by cybergsus on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1398798708

Comment:
Hey, I'm using PipeWire with its PulseAudio wrapper, and I got it to work. In case this helps, I made sure bluetoothd started before pipewire, enabling bluetoothd as a service and starting `pipewire` and `pipewire-pulse` from sway, once everything has started

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (14 preceding siblings ...)
  2023-01-24  9:39 ` cybergsus
@ 2023-01-24  9:39 ` cybergsus
  2023-01-24  9:43 ` cybergsus
                   ` (8 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: cybergsus @ 2023-01-24  9:39 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 465 bytes --]

New comment by cybergsus on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1401635178

Comment:

> I assume you have the same issue, right? Do you have libspa-bluetooth installed which was mentioned earlier in this thread? https://docs.voidlinux.org/config/media/pipewire.html#bluetooth-audio

Sure! I forgot to mention in my comment that what I did solved the issue. Changed the comment to avoid furrher confusion.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (15 preceding siblings ...)
  2023-01-24  9:39 ` cybergsus
@ 2023-01-24  9:43 ` cybergsus
  2023-01-24  9:43 ` cybergsus
                   ` (7 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: cybergsus @ 2023-01-24  9:43 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 521 bytes --]

New comment by cybergsus on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1398798708

Comment:
Hey, I'm using PipeWire with its PulseAudio wrapper, and I got it to work. In case this helps, I made sure bluetoothd started before pipewire, enabling bluetoothd as a service and starting `pipewire` and `pipewire-pulse` from sway, once everything has started. I use (under musl):

- `libspa-bluetooth-0.3.63_1`
- `libpipewire-0.3.63_1`
- `pipewire-0.3.63_1`
- `bluez-5.65_1`

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (16 preceding siblings ...)
  2023-01-24  9:43 ` cybergsus
@ 2023-01-24  9:43 ` cybergsus
  2023-02-20 21:18 ` dwhughes
                   ` (6 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: cybergsus @ 2023-01-24  9:43 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 539 bytes --]

New comment by cybergsus on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1398798708

Comment:
Hey, I'm using PipeWire with its PulseAudio wrapper, and I got it to work. In case this helps, I made sure bluetoothd started before pipewire, enabling bluetoothd as a service and starting `pipewire` and `pipewire-pulse` from sway, once everything has started. I use (under musl):

- `libspa-bluetooth-0.3.63_1`
- `libpipewire-0.3.63_1`
- `pipewire-0.3.63_1`
- `bluez-5.65_1`
- linux `6.1.6_1`

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (17 preceding siblings ...)
  2023-01-24  9:43 ` cybergsus
@ 2023-02-20 21:18 ` dwhughes
  2023-02-20 21:22 ` dwhughes
                   ` (5 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: dwhughes @ 2023-02-20 21:18 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 4523 bytes --]

New comment by dwhughes on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1437556594

Comment:
A few days ago my Bluetooth headphones stopped connecting with the same `br-connection-profile-unavailable` message.

I tried resetting the system state by first removing the device (`remove F8:4E:17:C3:AE:7E` in bluetoothctl), then powering down for half a minute, booting again and re-adding the device via `bluetoothctl`. No change in behaviour.

<details>
<summary>bluetoothctl session transcript (information from other devices elided)</summary>

```
[bluetooth]# scan on
[NEW] Device F8:4E:17:C3:AE:7E WH-1000XM4
[bluetooth]# pair F8:4E:17:C3:AE:7E
Attempting to pair with F8:4E:17:C3:AE:7E
[CHG] Device F8:4E:17:C3:AE:7E Connected: yes
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 81c2e72a-0591-443e-a1ff-05f988593351
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 8901dfa8-5c7e-4d8f-9f0c-c2b70683f5f0
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 931c7e8a-540f-4686-b798-e8df0a2ad9f7
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: f8d1fbe4-7966-4334-8024-ff96c9330e15
[CHG] Device F8:4E:17:C3:AE:7E ServicesResolved: yes
[CHG] Device F8:4E:17:C3:AE:7E Paired: yes
Pairing successful
[CHG] Device F8:4E:17:C3:AE:7E ServicesResolved: no
[CHG] Device F8:4E:17:C3:AE:7E Connected: no
[bluetooth]# trust F8:4E:17:C3:AE:7E
[CHG] Device F8:4E:17:C3:AE:7E Trusted: yes
Changing F8:4E:17:C3:AE:7E trust succeeded
[bluetooth]# connect F8:4E:17:C3:AE:7E
Attempting to connect to F8:4E:17:C3:AE:7E
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
```

</details>

I'm on Ubuntu Jammy, Linux 5.19.0-32-generic (with a heavily personalised SwayWM environment, but I hope that isn't relevant as it worked before and I'm _mostly_ sure I didn't change my environment).

**Package versions and recent changes:**

* bluez: 5.64-0ubuntu1
* pipewire: 0.3.48-1ubuntu3
* libspa*bluetooth: _not installed_

The absence of `libspa-0.2-bluetooth` etc. is presumably irrelevant as my system worked fine without it before.

I checked my `apt` history (`grep -e blue -e pipewire /var/log/apt/history.log`) and I see only one Pipewire- or Bluetooth-related change. Four days ago, I ran `apt install wireplumber` (I forget why) and this changed some packages:

```
Install: pipewire-pulse:amd64 (0.3.48-1ubuntu3, automatic), wireplumber:amd64 (0.4.8-4), libwireplumber-0.4-0:amd64 (0.4.8-4, automatic)
Remove: pipewire-media-session:amd64 (0.4.1-2ubuntu1)
```

I have tried to reverse this by running `apt install pipewire-media-session` (which forces uninstall of wireplumber) and re-running the powercycle-scan-pair-connect recipe above. No improvement.

**Other details:**

Kernel dmesg records no Bluetooth-related messages during the pairing/connection attempt.

`bluetooth.service` systemd journal says:

```
Feb 20 21:43:13 skierfe systemd[1]: Started Bluetooth service.
Feb 20 21:43:13 skierfe bluetoothd[1481]: Starting SDP server
Feb 20 21:43:13 skierfe bluetoothd[1481]: Bluetooth management interface 1.22 initialized
Feb 20 21:44:29 skierfe bluetoothd[1481]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for F8:4E:17:C3:AE:7E: Protocol not available
```

There are a lot of suggested fixes in this thread which seem unlikely to be effective (e.g. "install libspa-bluetooth", when my `apt` history shows that it wasn't installed previously). I would be grateful for advice on which tests to prioritise before I start confusing things with arbitrary changes.

I would _really really love_ if this behaviour could be made more transparent for an "average geek" user. The inscrutability of this error makes it difficult for someone like me, with some geek-fu but mediocre Bluetooth knowledge, to get traction on the issue.


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (18 preceding siblings ...)
  2023-02-20 21:18 ` dwhughes
@ 2023-02-20 21:22 ` dwhughes
  2023-08-21  5:46 ` GrubBox
                   ` (4 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: dwhughes @ 2023-02-20 21:22 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 4523 bytes --]

New comment by dwhughes on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1437556594

Comment:
A few days ago my Bluetooth headphones stopped connecting with the same `br-connection-profile-unavailable` message.

I tried resetting the system state by first removing the device (`remove F8:4E:17:C3:AE:7E` in bluetoothctl), then powering down for half a minute, booting again and re-adding the device via `bluetoothctl`. No change in behaviour.

<details>
<summary>bluetoothctl session transcript (information from other devices elided)</summary>

```
[bluetooth]# scan on
[NEW] Device F8:4E:17:C3:AE:7E WH-1000XM4
[bluetooth]# pair F8:4E:17:C3:AE:7E
Attempting to pair with F8:4E:17:C3:AE:7E
[CHG] Device F8:4E:17:C3:AE:7E Connected: yes
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 00000000-deca-fade-deca-deafdecacaff
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 81c2e72a-0591-443e-a1ff-05f988593351
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 8901dfa8-5c7e-4d8f-9f0c-c2b70683f5f0
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 931c7e8a-540f-4686-b798-e8df0a2ad9f7
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: 96cc203e-5068-46ad-b32d-e316f5e069ba
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: b9b213ce-eeab-49e4-8fd9-aa478ed1b26b
[CHG] Device F8:4E:17:C3:AE:7E UUIDs: f8d1fbe4-7966-4334-8024-ff96c9330e15
[CHG] Device F8:4E:17:C3:AE:7E ServicesResolved: yes
[CHG] Device F8:4E:17:C3:AE:7E Paired: yes
Pairing successful
[CHG] Device F8:4E:17:C3:AE:7E ServicesResolved: no
[CHG] Device F8:4E:17:C3:AE:7E Connected: no
[bluetooth]# trust F8:4E:17:C3:AE:7E
[CHG] Device F8:4E:17:C3:AE:7E Trusted: yes
Changing F8:4E:17:C3:AE:7E trust succeeded
[bluetooth]# connect F8:4E:17:C3:AE:7E
Attempting to connect to F8:4E:17:C3:AE:7E
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
```

</details>

I'm on Ubuntu Jammy, Linux 5.19.0-32-generic (with a heavily personalised SwayWM environment, but I hope that isn't relevant as it worked before and I'm _mostly_ sure I didn't change my environment).

**Package versions and recent changes:**

* bluez: 5.64-0ubuntu1
* pipewire: 0.3.48-1ubuntu3
* libspa*bluetooth: _not installed_

The absence of `libspa-0.2-bluetooth` etc. is presumably irrelevant as my system worked fine without it before.

I checked my `apt` history (`grep -e blue -e pipewire /var/log/apt/history.log`) and I see only one Pipewire- or Bluetooth-related change. Four days ago, I ran `apt install wireplumber` (I forget why) and this changed some packages:

```
Install: pipewire-pulse:amd64 (0.3.48-1ubuntu3, automatic), wireplumber:amd64 (0.4.8-4), libwireplumber-0.4-0:amd64 (0.4.8-4, automatic)
Remove: pipewire-media-session:amd64 (0.4.1-2ubuntu1)
```

I have tried to reverse this by running `apt install pipewire-media-session` (which forces uninstall of wireplumber) and re-running the powercycle-scan-pair-connect recipe above. No improvement.

**Other details:**

Kernel dmesg records no Bluetooth-related messages during the pairing/connection attempt.

`bluetooth.service` systemd journal says:

```
Feb 20 21:43:13 skierfe systemd[1]: Started Bluetooth service.
Feb 20 21:43:13 skierfe bluetoothd[1481]: Starting SDP server
Feb 20 21:43:13 skierfe bluetoothd[1481]: Bluetooth management interface 1.22 initialized
Feb 20 21:44:29 skierfe bluetoothd[1481]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for F8:4E:17:C3:AE:7E: Protocol not available
```

There are a lot of suggested fixes in this thread which seem unlikely to be effective (e.g. "install libspa-bluetooth", when my `apt` history shows that it wasn't installed previously). I would be grateful for advice on which tests to prioritise before I start confusing things with arbitrary changes.

I would _really really love_ if this behaviour could be made more transparent for an "average geek" user. The inscrutability of this error makes it difficult for someone like me, with some geek-fu but mediocre Bluetooth knowledge, to get traction on the issue.


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (19 preceding siblings ...)
  2023-02-20 21:22 ` dwhughes
@ 2023-08-21  5:46 ` GrubBox
  2023-08-21  5:48 ` GrubBox
                   ` (3 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: GrubBox @ 2023-08-21  5:46 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 571 bytes --]

New comment by GrubBox on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1685688991

Comment:
I have the same issue.  ```Failed to connect: org.bluez.Error.Failed br-connection-unknown```
It seems to happen when I use pipewire instead of pulseaudio.
Also I use my "realme Bud Wireless 2 Neo Handsfree" on multiple devices to each time it has to re-synchronize aka DUAL DEVICE SWITCH,  with each machine (iphone/mac/PC).  I am getting a new wireless device which has **Dual device pair** This could also be an issue. idk

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (20 preceding siblings ...)
  2023-08-21  5:46 ` GrubBox
@ 2023-08-21  5:48 ` GrubBox
  2023-08-21  5:48 ` GrubBox
                   ` (2 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: GrubBox @ 2023-08-21  5:48 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 607 bytes --]

New comment by GrubBox on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1685688991

Comment:
I have had the same issue.  ```Failed to connect: org.bluez.Error.Failed br-connection-unknown```
It seems to happen when I use _pipewire instead of pulseaudio_ .
Also I use my "realme Bud Wireless 2 Neo Handsfree" on multiple devices.
It has a feature call  **Dual Device Switch**.
So each time it has to re-synchronize , with each machine (iphone/mac/PC).  
I am getting a new wireless device which has **Dual device pair** This could also be an issue. idk

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (21 preceding siblings ...)
  2023-08-21  5:48 ` GrubBox
@ 2023-08-21  5:48 ` GrubBox
  2023-08-21  5:48 ` GrubBox
  2023-08-21  5:49 ` GrubBox
  24 siblings, 0 replies; 26+ messages in thread
From: GrubBox @ 2023-08-21  5:48 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 607 bytes --]

New comment by GrubBox on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1685688991

Comment:
I have had the same issue.  ```Failed to connect: org.bluez.Error.Failed br-connection-unknown```
It seems to happen when I use _pipewire instead of pulseaudio_ .
Also I use my "realme Bud Wireless 2 Neo Handsfree" on multiple devices.
It has a feature call  **Dual Device Switch**.
So each time it has to re-synchronize , with each machine (iphone/mac/PC).  
I am getting a new wireless device which has **Dual device pair** 
This may solve the issue -idk-

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (22 preceding siblings ...)
  2023-08-21  5:48 ` GrubBox
@ 2023-08-21  5:48 ` GrubBox
  2023-08-21  5:49 ` GrubBox
  24 siblings, 0 replies; 26+ messages in thread
From: GrubBox @ 2023-08-21  5:48 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 609 bytes --]

New comment by GrubBox on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1685688991

Comment:
I have had the same issue.  ```Failed to connect: org.bluez.Error.Failed br-connection-unknown```
It seems to happen when I use _pipewire instead of pulseaudio_ .
Also I use my "realme Bud Wireless 2 Neo Handsfree" on multiple devices.
It has a feature call  **Dual Device Switch**.
So each time it has to re-synchronize , with each machine (iphone/mac/PC).  
I am getting a new wireless device which has **Dual device pair** 
This may solve the issue - idk -

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
  2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
                   ` (23 preceding siblings ...)
  2023-08-21  5:48 ` GrubBox
@ 2023-08-21  5:49 ` GrubBox
  24 siblings, 0 replies; 26+ messages in thread
From: GrubBox @ 2023-08-21  5:49 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 607 bytes --]

New comment by GrubBox on void-packages repository

https://github.com/void-linux/void-packages/issues/40018#issuecomment-1685688991

Comment:
I have had the same issue.  ```Failed to connect: org.bluez.Error.Failed br-connection-unknown```
It seems to happen when I use _pipewire instead of pulseaudio_ .
Also I use my "realme Bud Wireless 2 Neo Handsfree" on multiple devices.
It has a feature call  **Dual Device Switch**.
So each time it has to re-synchronize , with each machine (iphone/mac/PC).  
I am getting a new wireless device which has **Dual device pair** 
This may solve the issue _idk_

^ permalink raw reply	[flat|nested] 26+ messages in thread

end of thread, other threads:[~2023-08-21  5:49 UTC | newest]

Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-18  8:30 [ISSUE] Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable LinArcX
2022-10-18 12:05 ` Duncaen
2022-10-18 12:27 ` LinArcX
2022-10-18 13:06 ` paper42
2022-10-18 15:55 ` LinArcX
2022-10-18 16:03 ` LinArcX
2022-10-18 16:14 ` LinArcX
2022-10-18 16:27 ` LinArcX
2022-10-26 23:11 ` runrin
2022-12-10  8:20 ` eoli3n
2022-12-10  8:24 ` eoli3n
2023-01-20 18:48 ` cybergsus
2023-01-20 18:49 ` cybergsus
2023-01-20 20:34 ` paper42
2023-01-24  9:38 ` cybergsus
2023-01-24  9:39 ` cybergsus
2023-01-24  9:39 ` cybergsus
2023-01-24  9:43 ` cybergsus
2023-01-24  9:43 ` cybergsus
2023-02-20 21:18 ` dwhughes
2023-02-20 21:22 ` dwhughes
2023-08-21  5:46 ` GrubBox
2023-08-21  5:48 ` GrubBox
2023-08-21  5:48 ` GrubBox
2023-08-21  5:48 ` GrubBox
2023-08-21  5:49 ` GrubBox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).