I did a fresh installation yesterday. Today I installed bluez, bluez-utils (not yet pulseaudio-bluetooth), and started bluetooth.service.
$ pacman -Ss bluez | grep installed
extra/bluez 5.62-1 [installed]
extra/bluez-libs 5.62-1 [installed]
extra/bluez-utils 5.62-1 [installed]Then I ran bluetoothctl, and was able to power on the controller, scan, find my headphones, pair with them and trust them.
After trusting them, i tried to connect, and bluetoothctl returned the error reported in the initial post: «br-connection-profile-unavailable».
So I found this post, installed pulseaudio-bluetooth, rebooted.
Now bluetoothctl says there is no default controller:
# bluetoothctl
Agent registered
[bluetooth]# power on
No default controller availablerfkill says that no device is blocked
# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: noI tried stopping bluetooth.service and starting it in debug mode (and it still says in one of the last lines «Number of controllers: 0»)
# /usr/lib/bluetooth/bluetoothd -n -d
bluetoothd[1218]: Bluetooth daemon 5.62
bluetoothd[1218]: src/main.c:parse_config() parsing /etc/bluetooth/main.conf
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cDiscoverableTimeoutu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cAlwaysPairableu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cPairableTimeoutu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cPrivacyu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cJustWorksRepairingu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cTemporaryTimeoutu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cNameu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cClassu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cDeviceIDu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cReverseServiceDiscoveryu201d in group u201cGeneralu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cCacheu201d in group u201cGATTu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cKeySizeu201d in group u201cGATTu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cExchangeMTUu201d in group u201cGATTu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cChannelsu201d in group u201cGATTu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cSessionModeu201d in group u201cAVDTPu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cStreamModeu201d in group u201cAVDTPu201d
bluetoothd[1218]: src/main.c:parse_config() Key file does not have key u201cRSSISamplingPeriodu201d in group u201cAdvMonu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cPageScanTypeu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cPageScanIntervalu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cPageScanWindowu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cInquiryScanTypeu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cInquiryScanIntervalu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cInquiryScanWindowu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cLinkSupervisionTimeoutu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cPageTimeoutu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cMinSniffIntervalu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cMaxSniffIntervalu201d in group u201cBRu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cMinAdvertisementIntervalu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cMaxAdvertisementIntervalu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cMultiAdvertisementRotationIntervalu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanIntervalAutoConnectu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanWindowAutoConnectu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanIntervalSuspendu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanWindowSuspendu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanIntervalDiscoveryu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanWindowDiscoveryu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanIntervalAdvMonitoru201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanWindowAdvMonitoru201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanIntervalConnectu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cScanWindowConnectu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key u201cMinConnectionIntervalu201d in group u201cLEu201d
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “MaxConnectionInterval” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “ConnectionLatency” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “ConnectionSupervisionTimeout” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “Autoconnecttimeout” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “AdvMonAllowlistScanDuration” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “AdvMonNoFilterScanDuration” in group “LE”
bluetoothd[1218]: src/main.c:parse_mode_config() Key file does not have key “EnableAdvMonInterleaveScan” in group “LE”
bluetoothd[1218]: src/adapter.c:adapter_init() sending read version command
bluetoothd[1218]: Starting SDP server
bluetoothd[1218]: src/sdpd-service.c:register_device_id() Adding device id record for 0002:1d6b:0246:053e
bluetoothd[1218]: src/plugin.c:plugin_init() Loading builtin plugins
bluetoothd[1218]: src/plugin.c:add_plugin() Loading hostname plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading wiimote plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading autopair plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading policy plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading a2dp plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading avrcp plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading network plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading input plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading hog plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading gap plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading scanparam plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading deviceinfo plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading midi plugin
bluetoothd[1218]: src/plugin.c:add_plugin() Loading battery plugin
bluetoothd[1218]: src/plugin.c:plugin_init() Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[1218]: profiles/input/suspend-none.c:suspend_init()
bluetoothd[1218]: profiles/network/manager.c:read_config() Config options: Security=true
bluetoothd[1218]: plugins/hostname.c:read_dmi_fallback() chassis: laptop
bluetoothd[1218]: plugins/hostname.c:read_dmi_fallback() major: 0x01 minor: 0x03
bluetoothd[1218]: src/main.c:main() Entering main loop
bluetoothd[1218]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 0 soft 0 hard 0
bluetoothd[1218]: Bluetooth management interface 1.21 initialized
bluetoothd[1218]: src/adapter.c:read_version_complete() sending read supported commands command
bluetoothd[1218]: src/adapter.c:read_version_complete() sending read index list command
bluetoothd[1218]: src/rfkill.c:rfkill_event() RFKILL event idx 1 type 2 op 0 soft 0 hard 0
bluetoothd[1218]: src/adapter.c:read_commands_complete() Number of commands: 84
bluetoothd[1218]: src/adapter.c:read_commands_complete() Number of events: 42
bluetoothd[1218]: src/adapter.c:read_commands_complete() enabling kernel-side connection control
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports the set_blocked_keys op
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports controller cap command
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports exp features
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports set system confic
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports ext adv commands
bluetoothd[1218]: src/adapter.c:read_commands_complete() kernel supports suspend/resume events
bluetoothd[1218]: src/adapter.c:read_index_list_complete() Number of controllers: 0
bluetoothd[1218]: src/profile.c:register_profile() sender :1.90
bluetoothd[1218]: src/profile.c:create_ext() Created "Headset unit"
bluetoothd[1218]: src/profile.c:register_profile() sender :1.90
bluetoothd[1218]: src/profile.c:create_ext() Created "Hands-Free Voice gateway"
bluetoothd[1218]: plugins/hostname.c:property_changed() static hostname: gear
bluetoothd[1218]: plugins/hostname.c:property_changed() pretty hostname:
bluetoothd[1218]: plugins/hostname.c:property_changed() chassis: laptopThe kernel does not report any error, apparently (there are no red messages), but it says: «No device address configured»
# dmesg | grep Bluetooth
[ 2.816296] Bluetooth: Core ver 2.22
[ 2.816312] Bluetooth: HCI device and connection manager initialized
[ 2.816314] Bluetooth: HCI socket layer initialized
[ 2.816316] Bluetooth: L2CAP socket layer initialized
[ 2.816318] Bluetooth: SCO socket layer initialized
[ 2.911024] Bluetooth: hci0: Firmware timestamp 2021.38 buildtype 1 build 31586
[ 2.912998] Bluetooth: hci0: No device address configured
[ 2.913880] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 2.913914] Bluetooth: hci0: Boot Address: 0x100800
[ 2.913915] Bluetooth: hci0: Firmware Version: 98-38.21
[ 2.913916] Bluetooth: hci0: Firmware already loaded
[ 2.921446] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2.921448] Bluetooth: BNEP filters: protocol multicast
[ 2.921450] Bluetooth: BNEP socket layer initializedI cannot think anything else that can help debug this issue.
The strange thing is that, before installing pulseaudio-bluetooth, i was able to use bluetoothctl up to a certain point. Then after installing it, i «lost» the default controller
Last edited by leonixyz (2021-10-31 14:56:40)
Trying to connect some wireless headphones to my laptop. They worked a couple days ago then stopped and I cant figure out why. Before that it would work for a few days then stop until I rebooted or just tried again after a few hours. Now it hasn’t worked for almost 2 weeks.
$ neofetch
OS: Arch Linux x86_64
Host: 20BU000AUS ThinkPad T450
Kernel: 5.17.7-zen1-2-zen
# Installed
bluez 5.64-2
bluez-firmware 1.2-9
bluez-hid2hci 5.64-2
bluez-libs 5.64-2
bluez-utils 5.64-2
hidapi 0.11.2-1
libldac 2.0.2.3-1
pulseaudio-bluetooth 15.0-4
sbc 1.5-2
$ bluetoothctl show
Powered: yes
Discoverable: no
Pairable: yes
$ bluetoothctl info 8D:40:4C:C6:73:A4
Device 8D:40:4C:C6:73:A4 (public)
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
$ bluetoothctl connect 8D:40:4C:C6:73:A4
Attempting to connect to 8D:40:4C:C6:73:A4
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
$ journalctl -u bluetooth
bluetoothd[13782]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 8D:40:4C:C6:73:A4: Protocol not available
$ systemctl list-unit-files | grep blue
UNIT FILE STATE VENDOR PRESET
bluetooth-mesh.service enabled disabled
bluetooth.service enabled disabled
dbus-org.bluez.mesh.service alias -
dbus-org.bluez.service alias -
bluetooth.target static -
$ lsmod | grep bluetooth
bluetooth 925696 31 btrtl,btmtk,btintel,btbcm,bnep,btusb
crc16 16384 1 bluetooth
rfkill 36864 6 iwlmvm,bluetooth,thinkpad_acpi,cfg80211
ecdh_generic 16384 2 bluetooth
asked May 19, 2022 at 0:10
DominicDominic
691 gold badge2 silver badges4 bronze badges
6
Looks like OP found a solution in the comments of the question, but for anyone else looking at this, for me it just took a systemctl --user enable pulseaudio and systemctl --user start pulseaudio to fix it.
answered Oct 20, 2022 at 4:50
Many sources recommend setting ControllerMode = bredr and AutoEnable = true in /etc/bluetooth/main.conf, which has worked for me on previous installs.
In this case however, I had to comment out the line ControllerMode = bredr to solve the «br-connection-profile-unavailable» error.
(both of these were on Arch, not sure what made the difference)
answered Jan 31 at 10:42
I am running UbuntuStudio with KDE Plasma, using last week’s release of 22.10. The new version now supports headsets, and I had been using an Anker Soundcore as stereo speakers, I’ve used it with ubuntu for years, but it is now recognized as a Headset. In the Audio Settings I could test the mono output, but I needed the stereo mode, so set out to see if that could be switched back, which required bluetoothctl and I also installed blueman, and I may have installed pulseaudio, but I think it was there already.
Whatever I did, I now see the bt device connected, but no sound device appears for it, and all of the built-in sound devices no longer show in the Audio System Settings. The built-ins show in lspci and in aplay -l
I tried following a guide here to «replace pulse with pipewire in 20.04» and it seemed to work, but the check-step failed:
$ pactl info
Connection failure: Connection refused
Troubleshooting guides here and here are all pulseaudio orientated, so I don’t know if I should run pulseaudio -D, and I can’t remove pulseaudio with apt without removing the desktop. That transition guide also recommended a systemctl mask on pulseaudio and to unmask pipewire. This may have been bad advice.
$fuser -v /dev/snd/*
produces nothing at all. I’ve reinstalled all packages with pipewire in the name, deleted my home .config/pulse and the /etc/pulseaudio (which was empty), rebooting between changes.
I noticed my syslog is filling up with this pair, once per second:
kdeconnectd[3040]: org.kde.pulseaudio: context kaput
plasmashell[2951]: org.kde.plasma.pulseaudio: context kaput
Google could not find any relevant links for «pulseaudio context kaput» and the pavucontrol that worked before now does not connect.This suggested the pulseaudio daemon is needed and be unmasked, and doing this, I now see my built-in devices, but not the bt. The Anker shows in the list as an Audio device, but connecting it responds:
# connect 08:EB:ED:26:06:22
Attempting to connect to 08:EB:ED:26:06:22
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
I haven’t found any useful references on these br-connection messages.
so mostly now I am confused and not sure what my next step should be. Is this a pulseaudio problem? or a pipewire problem? or a bluetooth problem? Or something else.
Bug #1966436 reported by
EdwardO
on 2022-03-25
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
|
bluez (Ubuntu)
|
Invalid |
Undecided |
Unassigned
|
||
|
pipewire (Ubuntu)
|
Invalid |
Undecided |
Unassigned
|
||
|
pulseaudio (Ubuntu)
|
Invalid |
Undecided |
Unassigned
|
Bug Description
How to reproduce:
> bluetoothctl scan on
Discovery started
…
> bluetoothctl connect 94:DB:56:8E:0B:96
Attempting to connect to 94:DB:56:8E:0B:96
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
> systemctl status bluetooth
bluetooth.service — Bluetooth service
Loaded: loaded
…
mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available
Notes:
kernel-5.15, bluez-5.64
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Dell Precision 3560
Unfortunately I did not test before upgrade to 22.04.
Tried installing pipewire-pulse, blueman, but this is lower-level.
There are reports of similar errors popping up in Arch and Manjaro recently:
https://bbs.archlinux.org/viewtopic.php?id=270465
https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Mar 25 12:56:34 2022
InstallationDate: Installed on 2022-03-04 (21 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS «Focal Fossa» — Release amd64 (20210209.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Precision 3560
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago)
dmi.bios.date: 09/13/2021
dmi.bios.release: 1.12
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.2
dmi.board.name: 095HH7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22:
dmi.product.family: Precision
dmi.product.name: Precision 3560
dmi.product.sku: 0A22
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:24189 acl:41 sco:0 events:519 errors:0
TX bytes:8252 acl:33 sco:0 commands:239 errors:0
modified.conffile..etc.cron.daily.apport: [deleted]
- PipeWire version (
pipewire --version): libpipewire 0.3.48 - Distribution and distribution version (
PRETTY_NAMEfrom/etc/os-release): Void Linux - Desktop Environment: herbstluftwm
- Kernel version (
uname -r): 5.16.16_1 - BlueZ version (
bluetoothctl --version): bluetoothctl: 5.63 -
lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 27c6:609c Goodix Technology Co., Ltd. Goodix USB2.0 MISC
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 004: ID 8087:0032 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub- Bluetooth devices:
Device D4:EC:AB:64:EC:96 V2040Description of Problem:
Bluetooth connection (testing with mobile as host and laptop as sound receiver), work and does not work.
It works if:
Installed package bluez libspa-bluetooth, enabled service bluetoothd dbus pipewire pipewire-pulse and rebooted (Note 1: does not work unless reboot). And any subsequent reboot it works by default. Restarting service bluetoothd, it still works, just need to connnect again.
sudo xbps-install -S dbus bluez libspa-bluetooth
for i in dbus bluetoothd pipewire pipewire-pulse; do sudo ln -s /etc/sv/$i /var/service; done
# at the moment does not work
[bluetooth]# connect D4:EC:AB:64:EC:96
Attempting to connect to D4:EC:AB:64:EC:96
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
sudo reboot
# works now
sudo sv restart bluetoothd
# still works, need to run `power on` then just connect as usual
sudo sv restart pipewire-pulse
# still works, nothing needed, no disconnectionAnd when does not work: At runtime when it was «working», restarted the pipewire service
sudo sv restart pipewire
# magically puts the following sequence at the bluetoothctl console and disconnects
[CHG] Controller F8:B5:4D:D7:15:6C Class: 0x004c010c
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C Class: 0x000c010c
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C Class: 0x0008010c
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C Class: 0x0000010c
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller F8:B5:4D:D7:15:6C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D4:EC:AB:64:EC:96 ServicesResolved: no
[CHG] Device D4:EC:AB:64:EC:96 Connected: no
# Now this happens
[bluetooth]# connect D4:EC:AB:64:EC:96
Attempting to connect to D4:EC:AB:64:EC:96
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable
# Now whatever I do, restart bluetoothd or pipewire-pulse services, in different sequences,
# or anything regardless, it "doesn't work", unless I reboot once again.
# Although when restarting bluetoothd service now, it stucks until the timeout (41s as measured by prompt),
# and then `le-connection-abort-by-local` (a different error)
sudo sv restart bluetoothd
[bluetooth]# connect D4:EC:AB:64:EC:96
Attempting to connect to D4:EC:AB:64:EC:96
Failed to connect: org.bluez.Error.Failed le-connection-abort-by-localNow, removing the libspa-bluetooth package does not break anything at runtime when
connected, or trying connecting, everything works, booting without the package does not let me connect, post install needs reboot as specified earlier.
Actual Results:
- Post installation of
libspa-bluetooth, unless rebooted, cannot connect. - Restarting
pipewirewhen connection was working, breaks everything and unless rebooted I couldn’t connect again.
Expected Results:
- Post installation of
libspa-bluetooth, it should not be required to reboot to make connection work. - Restarting
pipewireshould just make bluetooth connection available again.
Additional Info (as attachments):
Let me know if I need to provide this, also which state do I have to provide it.
-
pw-dump > pw-dump.log: - Bluetooth debug log, see here: