Bluetooth Adapter not working on Manjaro-i3

[romjan1412]

[Posting Again] new bluetooth adapter problem. I tested it windows 7+10+11 and It was working perfectly. But it didn’t work on my manjaro-i3 machine. This is what i’ve done so far,

1. installed bluez, bluez-utils, blueberry

2. loaded the btusb module
   lsmod | grep "btusb"

btusb                  69632  0
btrtl                  28672  1 btusb
btbcm                  20480  1 btusb
btintel                32768  1 btusb
bluetooth             733184  12 btrtl,btintel,btbcm,bnep,btusb

3. start/enable bluetooth.service

systemctl status bluetooth

output :

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: di>
     Active: active (running) since Thu 2022-01-27 16:09:28 +06; 3h 3min ago
       Docs: man:bluetoothd(8)
   Main PID: 694 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 14210)
     Memory: 2.1M
        CPU: 18ms
     CGroup: /system.slice/bluetooth.service
             └─694 /usr/lib/bluetooth/bluetoothd

Jan 27 16:09:28 Devil-PC systemd[1]: Starting Bluetooth service...
Jan 27 16:09:28 Devil-PC bluetoothd[694]: Bluetooth daemon 5.63
Jan 27 16:09:28 Devil-PC systemd[1]: Started Bluetooth service.
Jan 27 16:09:28 Devil-PC bluetoothd[694]: Starting SDP server
Jan 27 16:09:28 Devil-PC bluetoothd[694]: Bluetooth management interface 1.20 initialized
lines 1-17/17 (END)

4. bluetoothctl show

No default controller available

5. blueberry output

(blueberry.py:29072): com.linuxmint.blueberry-WARNING **: 19:17:28.671: Could not retrieve the BT adapter name with 'bt-adapter -i': Command '['timeout', '2s', 'bt-adapter', '-i']' died with <Signals.SIGABRT: 6>.
**
ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self))
timeout: the monitored command dumped core

(blueberry.py:29072): com.linuxmint.blueberry-WARNING **: 19:17:28.808: Could not retrieve the BT adapter name with 'bt-adapter -i': Command '['timeout', '2s', 'bt-adapter', '-i']' died with <Signals.SIGABRT: 6>.

Additional Information

• lspci’s output

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode]
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0)
00:1c.5 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #6 (rev f0)
00:1c.6 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #7 (rev f0)
00:1c.7 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #8 (rev f0)
00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation 200 Series PCH LPC Controller (B250)
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

• Journalctl -b | grep -i Blue

Jan 27 12:56:02 Devil-PC kernel: Bluetooth: Core ver 2.22
Jan 27 12:56:02 Devil-PC kernel: Bluetooth: HCI device and connection manager initialized
Jan 27 12:56:02 Devil-PC kernel: Bluetooth: HCI socket layer initialized
Jan 27 12:56:02 Devil-PC kernel: Bluetooth: L2CAP socket layer initialized
Jan 27 12:56:02 Devil-PC kernel: Bluetooth: SCO socket layer initialized
Jan 27 12:56:02 Devil-PC kernel: Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once...
Jan 27 16:09:28 Devil-PC systemd[1]: Starting Bluetooth service...
Jan 27 16:09:28 Devil-PC bluetoothd[694]: Bluetooth daemon 5.63
Jan 27 16:09:28 Devil-PC dbus-daemon[697]: Encountered error 'Unknown element <policy> at root of configuration file' while parsing '/etc/dbus-1/system.d/bluetooth.conf'
Jan 27 16:09:28 Devil-PC dbus-daemon[697]: dbus-daemon[697]: Encountered error 'Unknown element <policy> at root of configuration file' while parsing '/etc/dbus-1/system.d/bluetooth.conf'
Jan 27 16:09:28 Devil-PC systemd[1]: Started Bluetooth service.
Jan 27 16:09:28 Devil-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 27 16:09:28 Devil-PC systemd[1]: Reached target Bluetooth Support.
Jan 27 16:09:28 Devil-PC bluetoothd[694]: Starting SDP server
Jan 27 16:09:28 Devil-PC kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 27 16:09:28 Devil-PC kernel: Bluetooth: BNEP filters: protocol multicast
Jan 27 16:09:28 Devil-PC kernel: Bluetooth: BNEP socket layer initialized
Jan 27 16:09:28 Devil-PC bluetoothd[694]: Bluetooth management interface 1.20 initialized
Jan 27 16:09:28 Devil-PC NetworkManager[698]: <info>  [1643278168.5624] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.34.0-1/libnm-device-plugin-bluetooth.so)
Jan 27 16:09:33 Devil-PC kernel: Bluetooth: hci0: CSR: Failed to suspend the device for our Barrot 8041a02 receive-issue workaround
Jan 27 16:09:38 Devil-PC kernel: Bluetooth: hci0: setting interface failed (110)

System Information

inxi -F

System:
  Host: Devil-PC Kernel: 5.13.19-2-MANJARO x86_64 bits: 64 Desktop: i3 4.20.1
    Distro: Manjaro Linux
Machine:
  Type: Desktop System: Gigabyte product: B250M-D2V v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: B250M-D2V-CF v: x.x serial: <superuser required>
    UEFI: American Megatrends v: F8 date: 04/10/2018
CPU:
  Info: quad core model: Intel Core i5-7400 bits: 64 type: MCP cache:
    L2: 1024 KiB
  Speed (MHz): avg: 1024 min/max: 800/3500 cores: 1: 800 2: 800 3: 800
    4: 1699
Graphics:
  Device-1: Intel HD Graphics 630 driver: i915 v: kernel
  Display: x11 server: X.Org 1.21.1.3 driver: loaded: modesetting
    resolution: 1366x768~60Hz
  Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
  Device-1: Intel 200 Series PCH HD Audio driver: snd_hda_intel
  Device-2: C-Media USB Audio Device type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Sound Server-1: ALSA v: k5.13.19-2-MANJARO running: yes
  Sound Server-2: PulseAudio v: 15.0 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: e0:d5:5e:d0:e7:ca
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
    driver: btusb
  Report: bt-adapter ID: hci0 state: up address: N/A
Drives:
  Local Storage: total: 1.13 TiB used: 748.67 GiB (64.8%)
  ID-1: /dev/sda vendor: Toshiba model: HDWD110 size: 931.51 GiB
  ID-2: /dev/sdb vendor: GALAX model: GAMER L TA1D0240A size: 223.57 GiB
Partition:
  ID-1: / size: 110.94 GiB used: 92.65 GiB (83.5%) fs: ext4 dev: /dev/sdb5
  ID-2: /boot/efi size: 297 MiB used: 288 KiB (0.1%) fs: vfat
    dev: /dev/sdb7
Swap:
  ID-1: swap-1 type: partition size: 10 GiB used: 0 KiB (0.0%) dev: /dev/sdb6
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 177 Uptime: 39m Memory: 11.58 GiB used: 2.2 GiB (19.0%)
  Shell: Zsh inxi: 3.3.12

[andreas85]

This way nobody will answer because nobody will read this mess.

Please surround your logs with 3 backticks ``` to make them readable

In the following posts is described how to format your post so everybody kann read it easily

How to increase your chances of solving your issue:

[HowTo] Increase your chances of solving your issue

Difficulty: ★☆☆☆☆ Strong of its many members, the Manjaro support forum can provide you help whenever you have an issue with your Manjaro installation. But in order to work efficiently, we shall also ask you to follow three major steps. Keep calm and read First some basics: whenever you need to troubleshoot, chances are the solution is already under your nose. Find error messages Very often when an applications crashes, and sometimes when it misbehaves, it prints an error message somewhere. …

Please provide Information:

[HowTo] Provide System Information

Welcome to Manjaro! To allow all of us helpful people on this forum TO HELP YOU, we need some basic information about your system. This probably means you described the symptoms of your problem, but now we need some more information to know where the origin of your issue is exactly. Someone else probably linked you to this tutorial, so if you’re reading this in response to a question, please click the link above this text to bring you to the full and unabridged text of the tutorial…

Update:

Very Nice. Now the only thing missing is the output of inxi . And if you answer this time, instead of editing your first post, your Thread will go to the top again, where someone (with knowledge) may see it

[romjan1412]

Thanks for your replied information @andreas85 . I hope someone would notice it. My 200 taka (Bangladeshing Money) would go waste if i’m using it!