Arch Linux

d.ALT

Member

Registered: 2019-05-10

Posts: 951

DualSense bluetoothd control_connect_cb() Host is down (112)

<PLEASE NOTE>
DualSense is working perfectly fine via bluetooth!
I'm posting this topic out of sheer curiosity to simply understand what is going on...
</PLEASE NOTE>

Bluetooth < System Settings < KDE reports this error: br-connection-create-socket

$ ./dualsensectl info

$ ./dualsensectl info
Hardware: 617
Build date: Jan 29 2024 09:13:59
Firmware: 10c000a (type 3)
Fw version: 65596 131081 6
Sw series: 4
Update version: 0458

$ sudo journalctl -f -u bluetooth.service

dic 23 12:32:42 ARCH-RYZEN bluetoothd[676]: No matching connection for device
dic 23 12:32:48 ARCH-RYZEN bluetoothd[676]: profiles/input/device.c:control_connect_cb() connect to AC:36:1B:88:0D:EB: Host is down (112)
dic 23 12:33:25 ARCH-RYZEN bluetoothd[676]: No matching connection for device
dic 23 12:33:31 ARCH-RYZEN bluetoothd[676]: profiles/input/device.c:control_connect_cb() connect to AC:36:1B:88:0D:EB: Host is down (112)
dic 23 12:33:48 ARCH-RYZEN bluetoothd[676]: profiles/input/device.c:control_connect_cb() connect to AC:36:1B:88:0D:EB: Host is down (112)
dic 23 12:40:55 ARCH-RYZEN bluetoothd[676]: No matching connection for device
dic 23 12:41:01 ARCH-RYZEN bluetoothd[676]: profiles/input/device.c:control_connect_cb() connect to AC:36:1B:88:0D:EB: Host is down (112)
dic 23 12:41:17 ARCH-RYZEN bluetoothd[676]: profiles/input/device.c:control_connect_cb() connect to AC:36:1B:88:0D:EB: Host is down (112)

I wonder why establishing connection always fails on 1st attempt (it only happens on the first "fresh" pairing).
If DualSense has been previously already paired (and is therefore included among the associated and remembered devices), then I can connect to it on 1st attempt.

---

<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.