Bluetooth not quite working on a fresh installation EOS-KDE

General system Newbie
1

Hi,

I am trying to pair/connect to some bluetooth peripherals but though it seems that they get paired up but the connection to them fails. One is a Logitech Bluetooth Adapter that I use to connect to my speaker.

I tried to use bluetoothctl in a terminal and this is what I get:

bluetoothctl devices
Device 6E:A6:72:B4:06:15 6E-A6-72-B4-06-15
Device 68:D9:3C:8A:1A:CC 68-D9-3C-8A-1A-CC
Device D3:9D:4B:A0:50:A8 Hue Lamp
Device F8:77:B8:AC:A9:19 F8-77-B8-AC-A9-19
Device C0:28:8D:92:DF:CF Logitech BT Adapter
Device 64:30:BE:4E:10:B4 64-30-BE-4E-10-B4
Device F8:04:2E:DD:06:71 [TV] UE55JU6515
Device 57:8F:5B:B5:C1:C2 57-8F-5B-B5-C1-C2

sudo bluetoothctl pair C0:28:8D:92:DF:CF 

Attempting to pair with C0:28:8D:92:DF:CF
[CHG] Device C0:28:8D:92:DF:CF Connected: yes
[CHG] Device C0:28:8D:92:DF:CF UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device C0:28:8D:92:DF:CF ServicesResolved: yes
[CHG] Device C0:28:8D:92:DF:CF Paired: yes
Pairing successful

sudo bluetoothctl connect C0:28:8D:92:DF:CF 
Attempting to connect to C0:28:8D:92:DF:CF
Failed to connect: org.bluez.Error.Failed

I read about a package on an Arch forum thread: bluez-hid2hci. I installed it, but I can’t seem to get the connection.

inxi

System: Kernel: 5.8.2-zen1-1-zen x86_64 bits: 64 compiler: N/A Desktop: KDE Plasma 5.19.4 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM Distro: EndeavourOS

Machine: Type: Laptop System: Dell product: XPS 13 9380 v: N/A serial: Chassis: type: 10 serial:
Mobo: Dell model: 0KTDY6 v: A00 serial: UEFI: Dell v: 1.11.0 date: 07/06/2020

CPU: Info: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 8192 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31999
Speed: 500 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 593 2: 600 3: 600 4: 600 5: 600 6: 600 7: 600 8: 600

Graphics: Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0
Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus ID: 1-5:2 chip ID: 0c45:6723
Display: x11 server: X.Org 1.20.8 compositor: kwin_x11 driver: intel unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz s-dpi: 96
OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.6 direct render: Yes

Audio: Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1f.3
chip ID: 8086:9dc8
Sound Server: ALSA v: k5.8.2-zen1-1-zen

Network: Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
vendor: Bigfoot Networks Killer 1435 Wireless-AC driver: ath10k_pci v: kernel port: efa0 bus ID: 02:00.0
chip ID: 168c:003e
IF: wlan0 state: up mac:
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A

Please let me know if I should run any commands to give you the info you need. I appreciate greatly any help.

1 Like
2

Try here:

1 Like
3

Thanks @BONK for fast response!

I should have mentioned that I have bluez and bluez-utils installed.
The service is also enabled and running. I did even installed blueberry but it couldn’t make the connection. I didn’t bother with installing blueman since the CLI method recommended in that thread also failed.

I am not sure if there is something missing in the system or I have overlooked something. I should perhaps mention that this machine came with another Linux distro pre-installed and bluetooth was working then.

4

bluetoothctl is a cli tool not only a command to use better simple let the tool open:

sudo bluetoothctl
Agent registered
[CHG] Controller 00:15:83:3D:0A:57 Pairable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:15:83:3D:0A:57 Discovering: yes
[NEW] Device 00:12:3D:00:3D:1C BH-M30
[bluetooth]# pair 00:12:3D:00:3D:1C
Attempting to pair with 00:12:3D:00:3D:1C
[CHG] Device 00:12:3D:00:3D:1C Connected: yes
[CHG] Device 00:12:3D:00:3D:1C UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:12:3D:00:3D:1C UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 00:12:3D:00:3D:1C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:12:3D:00:3D:1C UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:12:3D:00:3D:1C ServicesResolved: yes
[CHG] Device 00:12:3D:00:3D:1C Paired: yes
Pairing successful
[CHG] Device 00:12:3D:00:3D:1C ServicesResolved: no
[CHG] Device 00:12:3D:00:3D:1C Connected: no
[bluetooth]# trust 00:12:3D:00:3D:1C
[CHG] Device 00:12:3D:00:3D:1C Trusted: yes
Changing 00:12:3D:00:3D:1C trust succeeded
[bluetooth]# connect 00:12:3D:00:3D:1C
Attempting to connect to 00:12:3D:00:3D:1C
[CHG] Device 00:12:3D:00:3D:1C Connected: yes
Connection successful
[CHG] Device 00:12:3D:00:3D:1C UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:12:3D:00:3D:1C UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 00:12:3D:00:3D:1C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 00:12:3D:00:3D:1C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:12:3D:00:3D:1C UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:12:3D:00:3D:1C ServicesResolved: yes
[BH-M30]#

you may simple miss to trust the device before connecting

1 Like
5

Thank’s @joekamprad for the instructions! I’ll try them a bit later on and report back.

6

Their has been a problem with bluetooth on Arch since kernel 5.8. not connecting to some apps,
Today testing delivered 5.8.3 now my connection problems are solved so wait a few days and it will be in stable if not sooner

7

@BONK, @joekamprad and @mandog

Thank you so much for your support and invaluable insight!
After some more digging, it looked like that I would need to install an additional package namely pulseaudio-bluetooth. After a reboot (just in case), the bluetooth devices got paired up and connected, streaming sweet music to my BT speaker. Sorry for the trouble for!

Now I can finally breath out!
:triumph:

8

Its always a good thing to glance at the Arch Wiki, but remember it always takes the higher ground and most steps are already implied some distros install every available deps, Arch does not leaving the user in total control unwasted RAM = more Ram available.

1 Like