Bluetooth dongle

I bought a USB Bluetooth dongle for my manjaro computer but unfortunately, this won’t be recognized when I plug it in.
Can anyone give me some advice, please?
Should I buy a new one that is compatible with manjaro?

how do you know?
how do you check whether it is recognized?

When I plug it in and use the Blueman I see no devices.
Let me know if I’m wrong or I can use another method to make sure

You are a long time member - and should know how to retrieve and provide information.

anyway

apart from info about your hardware
inxi -Fazy
preferably with the thing plugged in

you could use:

journalctl -f

in a terminal
and watch the output as you plug in
and disconnect
your device

you can do a similar thing with:

sudo dmesg -w
in a terminal

both commands will show you
in slightly different format
what the system sees when you plug in and remove the device

The most obvious thing to check (which I didn’t even think of until now) is:
is the bluetooth service started and running?

It might not be - because there was no bluetooth device when you installed the system and therefore no reason to configure the service.

The majority of bluetooth dongles works with Linux. Long time ago - years - I bought a cheap Deltaco bluétooth dongle - as I recall the price was around €8.

Check if it is recognized by listing USB devices

lsusb

Copy/paste the text from the terminal window into a reply - select the text and click the </> in the comment toolbar and click the reply button.

Example from my system with the Deltaco bt dongle

$ lsusb
 ...
Bus 001 Device 010: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
 ...

I’ve got this one:

Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

But still cannot use it on Blueman

inxi -Fazy:

System:
  Kernel: 5.15.50-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=3a81af0d-a5c0-428a-95b7-84fb1fa4afe9 rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.5 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME H510M-A v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 0820
    date: 04/27/2021
CPU:
  Info: model: Intel Core i3-10100 bits: 64 type: MT MCP arch: Comet Lake
    gen: core 10 built: 2020 process: Intel 14nm family: 6 model-id: 0xA5 (165)
    stepping: 3 microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 800 min/max: 800/4300 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 bogomips: 57616
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 status: Vulnerable: eIBRS with unprivileged eBPF
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ASUSTeK driver: nvidia
    v: 470.129.06 alternate: nouveau,nvidia_drm non-free: 470.xx+
    status: legacy-active (EOL~2023/24) arch: Fermi 2 process: TSMC 28nm
    built: 2010-16 pcie: gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 01:00.0
    chip-ID: 10de:128b class-ID: 0300
  Display: x11 server: X.Org v: 21.1.3 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 54 s-size: 903x508mm (35.55x20.00")
    s-diag: 1036mm (40.79")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 55
    size: 885x498mm (34.84x19.61") diag: 1015mm (39.98") modes: N/A
  OpenGL: renderer: NVIDIA GeForce GT 710/PCIe/SSE2
    v: 4.6.0 NVIDIA 470.129.06 direct render: Yes
Audio:
  Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:f0c8 class-ID: 0403
  Device-2: NVIDIA GK208 HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 8 bus-ID: 01:00.1
    chip-ID: 10de:0e0f class-ID: 0403
  Sound Server-1: ALSA v: k5.15.50-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.52 running: yes
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15fa class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc
    bus-ID: 1-9.3:5 chip-ID: 0cf3:9271 class-ID: ff00 serial: <filter>
  IF: wlp0s20f0u9u3 state: up mac: <filter>
  IF-ID-1: br-44843efba035 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IF-ID-2: br-83967b164190 state: down mac: <filter>
  IF-ID-3: docker0 state: down mac: <filter>
  IF-ID-4: veth8a39296 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-5: vethcdbf368 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB
    driver: btusb v: 0.8 bus-ID: 1-14:8 chip-ID: 0a12:0001 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 2 state: up address: N/A
Drives:
  Local Storage: total: 342.81 GiB used: 132.28 GiB (38.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SanDisk model: ADATA SX6000LNP
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: VC0S032Q temp: 33.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: A-Data model: SU650 size: 223.57 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD
    serial: <filter> rev: 01D2 scheme: GPT
Partition:
  ID-1: / raw-size: 145.25 GiB size: 141.91 GiB (97.70%)
    used: 44.22 GiB (31.2%) fs: ext4 dev: /dev/sda4 maj-min: 8:4
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 25.3 MiB (26.3%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 7.81 GiB used: 45.5 MiB (0.6%)
    priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 46.0 C mobo: N/A gpu: nvidia temp: 54 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 325 Uptime: 19m wakeups: 0 Memory: 7.62 GiB
  used: 5.86 GiB (76.9%) Init: systemd v: 251 default: graphical
  tool: systemctl Compilers: gcc: 12.1.0 clang: 13.0.1 Packages: 1344
  pacman: 1330 lib: 336 flatpak: 2 snap: 12 Shell: Zsh v: 5.9 default: Bash
  v: 5.1.16 running-in: yakuake inxi: 3.3.19

Maybe here is the problem:

sudo dmesg -w

[ 1390.441797] Bluetooth: hci0: CSR: Failed to suspend the device for our Barrot 8041a02 receive-issue workaround

… because my suggestion to check for it might have been overlooked:
is the service active?
systemctl status bluetooth.service

Yes, active and running
But still can’t use it.

It has the same device id as mine - and I have no issues connecting.

Albeit not blueman but bluedevil on KDE - you may need to do some low level troubleshooting

Check if you have bluez-utils package installed - otherwise install it

which bluetoothctl

Execute the command bluetoothctl which will open a bluetooth controller environment

list

Ensure the controller is powered

power on

Then scan for devices

scan on

Then stop scanning when you have seen it working

scan off

When I use list command on bluetoothctlenvironment I get nothing.
Also after using power on I get an error: No default controller available
And same error for scan on command

Then you have other issues

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 010: ID 046d:0a44 Logitech, Inc. Headset H390
Bus 001 Device 008: ID 0451:8242 Texas Instruments, Inc. 
Bus 001 Device 006: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 0bc2:ab24 Seagate RSS LLC Backup Plus Portable Drive
Bus 001 Device 004: ID 060b:2312 Solid Year nkey Mechanic LED
Bus 001 Device 002: ID 1532:0060 Razer USA, Ltd RZ01-0213 Gaming Mouse [Lancehead Tournament Edition]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ bluetoothctl
Agent registered
[bluetooth]# list
Controller 00:1A:7D:DA:71:0F tiger [default]
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:0F Discovering: yes
[NEW] Device 76:F7:48:A6:CA:E7 76-F7-48-A6-CA-E7
[NEW] Device 5A:04:CF:99:F6:3E 5A-04-CF-99-F6-3E
# help
Menu main:
Available commands:
-------------------
advertise                                         Advertise Options Submenu
monitor                                           Advertisement Monitor Options Submenu
scan                                              Scan Options Submenu
gatt                                              Generic Attribute Submenu
admin                                             Admin Policy Submenu
list                                              List available controllers
show [ctrl]                                       Controller information
select <ctrl>                                     Select default controller
devices                                           List available devices
paired-devices                                    List paired devices
system-alias <name>                               Set controller alias
reset-alias                                       Reset controller alias
power <on/off>                                    Set controller power
pairable <on/off>                                 Set controller pairable mode
discoverable <on/off>                             Set controller discoverable mode
discoverable-timeout [value]                      Set discoverable timeout
agent <on/off/capability>                         Enable/disable agent with given capability
default-agent                                     Set agent as the default one
advertise <on/off/type>                           Enable/disable advertising with given type
set-alias <alias>                                 Set device alias
scan <on/off/bredr/le>                            Scan for devices
info [dev]                                        Device information
pair [dev]                                        Pair with device
cancel-pairing [dev]                              Cancel pairing with device
trust [dev]                                       Trust device
untrust [dev]                                     Untrust device
block [dev]                                       Block device
unblock [dev]                                     Unblock device
remove <dev>                                      Remove device
connect <dev>                                     Connect device
disconnect [dev]                                  Disconnect device
menu <name>                                       Select submenu
version                                           Display version
quit                                              Quit program
exit                                              Quit program
help                                              Display help about this program
export                                            Print environment variables

Can help me to solve the problem(s), please?

I have no idea …