void-linux / void-linux/void-packages
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 5.19.16_1 x86_64 GenuineIntel notuptodate hold rFFF
Package(s) Affected
bluez
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 the 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
- install these packages first:
bluez
dbus
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked upstream BlueZ issue 351, then reproduce the failure with bluetoothctl using the listed bluez, dbus, PipeWire, PulseAudio, and Blueman setup. Check whether the same br-connection-profile-unavailable error occurs across devices; done means identifying a Void-specific cause and documenting or validating the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100