You are not logged in.

#1 2019-03-31 12:55:05

AlmostSurelyRob
Member
From: UK
Registered: 2012-03-17
Posts: 77

Bluetooth devices diconnect immediately upon connection

I am having an issue with one of my two arch laptops. I am trying to connect to bluetooth speaker. Laptop A works fine, but laptop B disconnects 2-3s after connecting. Both laptops have pulse installed so I don't think this should be a software issue, but something in the configuration. I have compared .asoundrc, /etc/pulse/system.pa files and they're the same.

When I try to connect through bluetoothctl, I get the following output.

Attempting to connect to 17:1A:5E:B1:0A:A5
Connection successful
[CHG] Device 17:1A:5E:B1:0A:A5 ServicesResolved: yes
[CHG] Controller 4C:EB:42:A9:38:81 Class: 0x00000000
[CHG] Device 17:1A:5E:B1:0A:A5 ServicesResolved: no
[CHG] Device 17:1A:5E:B1:0A:A5 Connected: no
[CHG] Controller 4C:EB:42:A9:38:81 Powered: no
[CHG] Controller 4C:EB:42:A9:38:81 Discovering: no
[DEL] Device 17:1A:5E:B1:0A:A5 RD-D328B
[DEL] Controller 4C:EB:42:A9:38:81 avignon [default]
[NEW] Controller 4C:EB:42:A9:38:81 avignon [default]
[NEW] Device 17:1A:5E:B1:0A:A5 RD-D328B
[CHG] Controller 4C:EB:42:A9:38:81 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:EB:42:A9:38:81 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:EB:42:A9:38:81 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:EB:42:A9:38:81 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:EB:42:A9:38:81 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:EB:42:A9:38:81 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:EB:42:A9:38:81 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:EB:42:A9:38:81 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:EB:42:A9:38:81 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb

I also looked at the output of journalctl and spotted this strange rfkill commands, but when I look at rfkill on this laptop all devices are visible and unblocked.

Mar 31 13:32:47 avignon bluetoothd[6339]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink
Mar 31 13:32:47 avignon systemd[1]: Starting Load/Save RF Kill Switch Status...
Mar 31 13:32:47 avignon systemd[1]: Stopped target Bluetooth.
Mar 31 13:32:47 avignon systemd[1]: Started Load/Save RF Kill Switch Status.
Mar 31 13:32:47 avignon audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/s>
Mar 31 13:32:47 avignon kernel: audit: type=1130 audit(1554035567.182:63): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill com>
Mar 31 13:32:47 avignon kernel: usb 2-11: new full-speed USB device number 12 using xhci_hcd
Mar 31 13:32:47 avignon kernel: usb 2-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
Mar 31 13:32:47 avignon kernel: usb 2-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 31 13:32:47 avignon kernel: Bluetooth: hci0: read Intel version: 3707100180012d0d2a
Mar 31 13:32:47 avignon kernel: Bluetooth: hci0: Intel device is already patched. patch num: 2a
Mar 31 13:32:47 avignon systemd[1]: Reached target Bluetooth.
Mar 31 13:32:47 avignon bluetoothd[6339]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource
Mar 31 13:32:47 avignon bluetoothd[6339]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink
Mar 31 13:32:52 avignon systemd[1]: systemd-rfkill.service: Succeeded.
Mar 31 13:32:52 avignon audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/sy>
Mar 31 13:32:52 avignon kernel: audit: type=1131 audit(1554035572.599:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill com>
Mar 31 13:32:58 avignon sudo[9710]: pam_unix(sudo:session): session closed for user root

Is there anyway I can eliminate hardware failure as a reason? I would appreciate any feedback.

Offline

Board footer

Powered by FluxBB