My Bluetooth not working

LaQuirrELL · January 10, 2023, 6:54pm

Got a pair of bluetooth headphones for xmas and am trying to install them.
Bought an ASUS bluetooth 5.0 adapter [USB-BT500]and plugged it in but it does not start.
Am not too savy on this bluetooth. Do I need to start something or is bluetooth auto started?
I don’t see any bluetooth icon on the desktop/taskbar/system tray, although I do see bluetooth network manager and bluez installed in software management thru Yast. This is all different from the last time I posted and I can’t seem to find the icon for “code”.
Info that may be required [from reading other posts about bluetooth]:
dabud@localhost:~> sudo rfkill list all
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
dabud@localhost:~>
dabud@localhost:~> lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0b05:190e ASUSTek Computer, Inc. ASUS USB-BT500
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 006: ID 046d:c077 Logitech, Inc. Mouse
Bus 001 Device 005: ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard
Bus 001 Device 004: ID 08bb:2707 Texas Instruments PCM2707 stereo audio DAC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
dabud@localhost:~> bluetoothctl
Agent registered
[CHG] Controller 58:11:22:53:17:AE Pairable: yes
[bluetooth]# exit

dabud@localhost:~> bluetoothctl
Agent registered
[CHG] Controller 58:11:22:53:17:AE Pairable: yes
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[bluetooth]# exit

dabud@localhost:~> lspci
00:00.0 Host bridge: Intel Corporation 8th/9th Gen Core 8-core Desktop Processor
Host Bridge/DRAM Registers [Coffee Lake S] (rev 0a)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphi
cs 630]
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Contr
oller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controll
er (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (
rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (
rev f0)
00:1b.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (
rev f0)
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (r
ev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (r
ev f0)
00:1f.0 ISA bridge: Intel Corporation Z390 Chipset LPC/eSPI Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (
rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (re
v 10)
02:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/SN750 / PC SN7
20 NVMe SSD
04:00.0 Non-Volatile memory controller: Sandisk Corp WD PC SN810 / Black SN850 NV
Me SSD (rev 01)
dabud@localhost:~>

marel · January 10, 2023, 9:31pm

Are you using KDE or Gnome?

I am running KDE and I have a Bluetooth icon in the lower bar:

It is not a good sign you get “Failed to start discovery: org.bluez.Error.NotReady” after “scan on”, for me that gives:

[bluetooth]# scan on
Discovery started
[CHG] Controller 00:7A:1D:DF:26:13 Discovering: yes
[CHG] Device A4:37:7C:A9:22:05 RSSI: -71

The “bluez” packages I have installed:

> sudo zypper se -i bluez

S  | Name              | Summary                                          | Type
---+-------------------+--------------------------------------------------+--------
i  | bluez             | Bluetooth Stack for Linux                        | package
i  | bluez-cups        | CUPS Driver for Bluetooth Printers               | package
i+ | bluez-obexd       | Object Exchange daemon for sharing content       | package
i  | bluez-qt-imports  | Async Bluez wrapper library                      | package
i  | bluez-qt-udev     | bluez-qt integration with udev                   | package
i+ | bluez-test        | Tools for testing of various Bluetooth-functions | package
i  | libKF5BluezQt6    | Async Bluez wrapper library - development files  | package
i+ | python310-pybluez | A Python Bluetooth wrapper                       | package

NB: Please use the Preformatted Text (Ctrl-E) button for command line output, that makes things better readable.

malcolmlewis · January 10, 2023, 9:42pm

@LaQuirrELL you need to unblock with rfkil as it’s softblocked;

0: hci0: Bluetooth
Soft blocked: yes

Or use blutoothctl power on

LaQuirrELL · January 11, 2023, 2:30pm

Thank you Marel for responding. I am using KDE. I DO NOT have a bluetooth icon in System Tray or in Settings.

This is what “sudo zypper se -i bluez” shows:

[code]dabud@localhost:~> sudo zypper se -i bluez
Loading repository data…
Reading installed packages…

However when I go to Yast> Software Management this is what shows installed:

Thank You malcolmlewis for responding.
The result of “blutoothctl power on”
dabud@localhost:~> bluetoothctl power on
Failed to set power on: org.bluez.Error.Failed
dabud@localhost:~>

Also, when I did "sudo systemctl status bluetooth ":
dabud@localhost:~> sudo systemctl status bluetooth
[sudo] password for root:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset:>
Active: active (running) since Tue 2023-01-10 14:02:48 EST; 18h ago
Docs: man:bluetoothd(8)
Main PID: 868 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 4915)
CPU: 24ms
CGroup: /system.slice/bluetooth.service
└─868 /usr/libexec/bluetooth/bluetoothd

Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
Jan 10 14:03:06 localhost.localdomain bluetoothd[868]: Endpoint registered: send>
dabud@localhost:~>

*So it shows that bluetooth has Failed to turn on, yet it shows it is Running? *
Or am I reading that wrong?

I am not sure if I am presenting the info correctly. Is there a set of rules for this forum, as in how to present code, etc.? Or does it do it as a matter of course? Thanks

malcolmlewis · January 11, 2023, 2:59pm

@LaQuirrELL then use rfkill to unblock, then should be fine with blurtoothctl, else if on a laptop, then may be a key combination that’s holding it back from soft unblock…

LaQuirrELL · January 16, 2023, 8:51pm

Not on laptop malcolmlewis.
I performed:
$ sudo rfkill unblock bluetooth
and it said unblocked in the Soft column when :
$ sudo rfkill

I now have a “bluetooth” icon in the system tray, but when I try to connect the dongle that shows in bluetooth, it says “failed to connect”.
Is there a way to uninstall everything bluetooth and start again? or something else?
Thanks

malcolmlewis · January 16, 2023, 10:22pm

@LaQuirrELL if you run the command bluetoothctl (as your user) and then run the command scan, does it start working?

LaQuirrELL · January 17, 2023, 2:07am

I will check and get back to you malcolmlewis

LaQuirrELL · January 17, 2023, 3:20am

@malcolmlewis This is what happens:

dabud@localhost:~> bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 5C:F3:70:7C:64:27 Discovering: yes
[NEW] Device C7:B8:24:67:D1:43 C7-B8-24-67-D1-43
[CHG] Device C7:B8:24:67:D1:43 RSSI: -84
[bluetooth]# connect C7:B8:24:67:D1:43
Attempting to connect to C7:B8:24:67:D1:43
[CHG] Device C7:B8:24:67:D1:43 Connected: yes
Failed to connect: org.bluez.Error.Failed le-connection-abort-by-local
[CHG] Device C7:B8:24:67:D1:43 Connected: no
[CHG] Device C7:B8:24:67:D1:43 UUIDs: 0000feed-0000-1000-8000-00805f9b34fb
[CHG] Device C7:B8:24:67:D1:43 RSSI: -92
[bluetooth]#

How do i tell what device Device C7:B8:24:67:D1:43 is?
I know it is a mac address, but not all devices have it marked?

Also, ran across this info, if it helps at all.

dabud@localhost:~> sudo systemctl status bluetooth
[sudo] password for root:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset:>
Active: active (running) since Sun 2023-01-15 04:51:07 EST; 1 day 17h ago
Docs: man:bluetoothd(8)
Main PID: 874 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 4915)
CPU: 34ms
CGroup: /system.slice/bluetooth.service
└─874 /usr/libexec/bluetooth/bluetoothd

Jan 15 04:51:18 localhost.localdomain bluetoothd[874]: Endpoint registered: send>
Jan 15 04:51:18 localhost.localdomain bluetoothd[874]: Endpoint registered: send>
Jan 15 04:51:18 localhost.localdomain bluetoothd[874]: Endpoint registered: send>
Jan 15 04:51:18 localhost.localdomain bluetoothd[874]: Endpoint registered: send>
Jan 15 04:51:18 localhost.localdomain bluetoothd[874]: Endpoint registered: send>
Jan 15 04:51:24 localhost.localdomain bluetoothd[874]: src/profile.c:record_cb()>
Jan 16 11:29:27 localhost.localdomain bluetoothd[874]: src/profile.c:record_cb()>
Jan 16 11:30:13 localhost.localdomain bluetoothd[874]: src/profile.c:record_cb()>
Jan 16 15:44:25 localhost.localdomain bluetoothd[874]: src/profile.c:record_cb()>
Jan 16 21:44:03 localhost.localdomain bluetoothd[874]: src/profile.c:record_cb()>
lines 1-21/21 (END)

malcolmlewis · January 17, 2023, 3:33am

@LaQuirrELL use pair C7:B8:24:67:D1:43 first, then it should pop up the device on connect.

LaQuirrELL · January 17, 2023, 4:27am

Thank you malcolmlewis.
Of course it must be paired 1st, before connect.
Onward.

your help is appreciated.

LaQuirrELL · January 17, 2023, 4:21pm

@malcolmlewis
the result of trying to pair the scanned device:

dabud@localhost:~> bluetoothctl
Agent registered
[bluetooth]# scan on
Discovery started
[CHG] Controller 5C:F3:70:7C:64:27 Discovering: yes
[NEW] Device C7:B8:24:67:D1:43 C7-B8-24-67-D1-43
[bluetooth]# pair C7:B8:24:67:D1:43
Attempting to pair with C7:B8:24:67:D1:43
[CHG] Device C7:B8:24:67:D1:43 Connected: yes
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[CHG] Device C7:B8:24:67:D1:43 Connected: no
[CHG] Device C7:B8:24:67:D1:43 UUIDs: 0000feed-0000-1000-8000-00805f9b34fb
[DEL] Device C7:B8:24:67:D1:43 C7-B8-24-67-D1-43
[NEW] Device C7:B8:24:67:D1:43 C7-B8-24-67-D1-43
[DEL] Device C7:B8:24:67:D1:43 C7-B8-24-67-D1-43
[NEW] Device C7:B8:24:67:D1:43 C7-B8-24-67-D1-43
[DEL] Device C7:B8:24:67:D1:43 C7-B8-24-67-D1-43
[bluetooth]#

Not sure how to check why it will not pair.
Also, bluetooth is not picking up any other BT devices [I have 2 other]
Is it possible that there may be some file[?] missing in bluetooth?
How could i check?

malcolmlewis · January 17, 2023, 5:30pm

@LaQuirrELL is the device your connecting to enabled for scanning/pairing? Some devices require confirmation (or a button press when being scanned)…

LaQuirrELL · January 17, 2023, 7:05pm

The device, AFAIK, is the Bluetooth dongle.
I will check to see again, but I did not receive a request to pair on my desktop.
I do not get a request to pair when I try to pair Device C7:B8:24:67:D1:43.
When I scan it shows 1 device [Device C7:B8:24:67:D1:43] and 1 controller [Controller 5C:F3:70:7C:64:27].
Is the controller the ‘bluetooth driver’ or is it the dongle?
How can I tell what the device is being scanned?

malcolmlewis · January 17, 2023, 10:24pm

@LaQuirrELL The controller is the dongle, at the blutoothctl [CHG]# prompt, just type help to see. For controller info show, for the other info C7:B8:24:67:D1:43 , devices will show paired etc.

LaQuirrELL · January 18, 2023, 4:28pm

Thank you @ malcolmlewis ,

just type helpwas a big help. I turned another Bluetooth device in and it showed up and actually told me what it was [Hesh 2 headset]. Unfortunately, when I tried to pair it it refused.
[bluetooth]# pair D0:8A:55:A4:9A:AF
Device D0:8A:55:A4:9A:AF not available
[bluetooth]#
I tried to find out what my original device C7:B8:24:67:D1:43 was, but this happened:
[bluetooth]# info C7:B8:24:67:D1:43
Device C7:B8:24:67:D1:43 not available
Is there something I am not starting/turning on?
AFAIK the device in question is turned on.