Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67652 - Can not connect to airpod pros via bluetooth

Attached to Project: Arch Linux
Opened by David Wiedemann (dadaurs) - Thursday, 20 August 2020, 17:46 GMT
Last edited by freswa (frederik) - Friday, 21 August 2020, 11:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To freswa (frederik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Ever since updating a few days ago, connecting my airpod pros via bluetooth fails.


If I delete the device and repair it, it does connect for the first time but the second time.

That being said, even the pairing process doesn't work every time.

I've decided I wouldn't attach a log file but rather copy paste relevant bits of info directly into here.

I'm using a lemur pro laptop, the spec for the Network controller(which does wifi+bluetooth iirc) is:
Network controller: Intel Corporation Wireless-AC 9462.

Here's what I've tried so far in no particular order.
When connecting with bluetoothctl, here's what I get:

[bluetooth]# connect 60:83:73:A8:8F:50
Attempting to connect to 60:83:73:A8:8F:50
[CHG] Device 60:83:73:A8:8F:50 Connected: yes
[CHG] Device 60:83:73:A8:8F:50 Connected: no
Failed to connect: org.bluez.Error.Failed
[CHG] Device 60:83:73:A8:8F:50 Connected: yes
[CHG] Device 60:83:73:A8:8F:50 Connected: no

Even though it indicates it is connected, the audio sink for the bluetooth devices does NOT appear in pavucontrol (nor in `pactl list sinks`), it finally disconnects again.

It is worth noting that, every time I do this, a new line appears in `systemctl status bluetooth` which is:
Aug 20 19:00:26 sys76 bluetoothd[57024]: connect error: Connection reset by peer (104)

I have also tried connecting via blueman-manager(while running blueman-applet), which gives the error
Connection Failed: Resource temporarily unavailable.

I've tried playing around with pulseaudio modules(enabling/disabling those which seem relevant)

I've also tried changing the controllermode variable in /etc/bluetooth.d/main.conf, to no avail.
I've used both pulseaudio bluetooth packages(ie pulseaudio-bluetooth and pulseaudio-modules-bt)

I've tried disabling ssp with btmgt, running `btmgmt ssp off` gives
Set Secure Simple Pairing for hci0 failed with status 0x0a (Busy)

Finally, I've gone into the /sys/class/bluetooth/hci0 directory to check out the files there, here's what
`
for file in power/*; do
echo $file:
cat $file
done
`
gives:
```
power/async :
disabled
power/autosuspend_delay_ms :
cat: power/autosuspend_delay_ms: Input/output error
power/control :
auto
power/runtime_active_kids :
0
power/runtime_active_time :
0
power/runtime_enabled :
disabled
power/runtime_status :
unsupported
power/runtime_suspended_time :
0
power/runtime_usage :
0
```
This seems somewhat strange to me.

Any help would be greatly appreciated, thank you.


Additional info:
* package version(s)
pulseaudio version is 13.0
This task depends upon

Closed by  freswa (frederik)
Friday, 21 August 2020, 11:36 GMT
Reason for closing:  None
Additional comments about closing:  Works with vanilla 5.9.0-rc1 reporter used the zen kernel.
Comment by loqs (loqs) - Thursday, 20 August 2020, 19:23 GMT
 FS#67502  ?
Comment by David Wiedemann (dadaurs) - Thursday, 20 August 2020, 20:04 GMT
It doesn't seem to be the same issue because:

-bluetoothd is not segfaulting in my case

-The issue didn't appear after a kernel update.

Comment by loqs (loqs) - Thursday, 20 August 2020, 20:22 GMT
What packages were in the update? Does downgrading those packages to the old versions restore old behavior?
Comment by freswa (frederik) - Thursday, 20 August 2020, 23:16 GMT
Please try linux 5.8.2 from testing.
Comment by David Wiedemann (dadaurs) - Friday, 21 August 2020, 11:33 GMT
Mhm yes indeed it seems that when I use the linux-git kernel from the AUR, bluetooth works flawlessly.

I didn't want to enable the testing repositories so I used the AUR.

As quick info, `uname -r` gives `5.9.0-rc1-1-git-00109-gda2968ff879b`.

I was using linux-zen, which I forgot to mention before so it might've been because of that.

Anyway thanks a lot for your help,



Loading...