Bluetooth on Manjaro Gnome Doesn't Work

~ $ blueman-manager 
blueman-manager version 2.1.3 starting
blueman-manager 07.37.00 ERROR    Manager:118 on_dbus_name_appeared: Default adapter not found, trying first available.
blueman-manager 07.37.00 ERROR    Manager:122 on_dbus_name_appeared: No adapter(s) found, exiting
~ $ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Fri 2020-09-25 07:28:21 MDT; 20min ago
       Docs: man:bluetoothd(8)
   Main PID: 2495 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 9174)
     Memory: 2.2M
     CGroup: /system.slice/bluetooth.service
             └─2495 /usr/lib/bluetooth/bluetoothd

Sep 25 07:28:21 f0xy systemd[1]: Starting Bluetooth service...
Sep 25 07:28:21 f0xy bluetoothd[2495]: Bluetooth daemon 5.54
Sep 25 07:28:21 f0xy systemd[1]: Started Bluetooth service.
Sep 25 07:28:21 f0xy bluetoothd[2495]: Starting SDP server
Sep 25 07:28:21 f0xy bluetoothd[2495]: Bluetooth management interface 1.14 initialized
~ $ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
~ $ lsmod | grep blue
bluetooth             688128  7 bnep
ecdh_generic           16384  1 bluetooth
rfkill                 28672  10 bluetooth,thinkpad_acpi,cfg80211
crc16                  16384  2 bluetooth,ext4

I’m unsure what I need to be looking for with this issue. I would deeply appreciate any help.

Welcome to the forum! :wave:

Please post your system information as outlined here:

~ $ inxi -Fazy
System:
  Kernel: 5.4.64-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.4-x86_64 
  root=UUID=2181dd6e-7f15-4e53-a132-18ce3339dc11 rw quiet 
  resume=UUID=eceb7ec0-b976-4363-9a56-755f626ec4d0 
  Desktop: GNOME 3.36.6 tk: GTK 3.24.23 wm: gnome-shell dm: GDM 3.36.3 
  Distro: Manjaro Linux 
Machine:
  Type: Laptop System: LENOVO product: 20BVCTO1WW v: ThinkPad T450 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: LENOVO model: 20BVCTO1WW v: SDK0E50512 STD serial: <filter> 
  UEFI [Legacy]: LENOVO v: JBET49WW (1.14 ) date: 05/21/2015 
Battery:
  ID-1: BAT0 charge: 0.9 Wh condition: 14.3/23.2 Wh (62%) volts: 10.4/11.1 
  model: SANYO 45N1773 type: Li-ion serial: <filter> status: Discharging 
  ID-2: BAT1 charge: 0.7 Wh condition: 17.9/23.5 Wh (76%) volts: 11.1/11.4 
  model: LGC 45N1127 type: Li-ion serial: <filter> status: Unknown 
CPU:
  Topology: Dual Core model: Intel Core i5-5200U bits: 64 type: MT MCP 
  arch: Broadwell family: 6 model-id: 3D (61) stepping: 4 microcode: 2F 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 17566 
  Speed: 1051 MHz min/max: 500/2700 MHz Core speeds (MHz): 1: 935 2: 942 
  3: 949 4: 974 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  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 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel HD Graphics 5500 vendor: Lenovo driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:1616 
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus ID: 1-8:4 
  chip ID: 04f2:b449 serial: <filter> 
  Display: x11 server: X.org 1.20.8 compositor: gnome-shell driver: intel 
  unloaded: modesetting alternate: fbdev,vesa resolution: <xdpyinfo missing> 
  OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.1.7 
  direct render: Yes 
Audio:
  Device-1: Intel Broadwell-U Audio vendor: Lenovo driver: snd_hda_intel 
  v: kernel bus ID: 00:03.0 chip ID: 8086:160c 
  Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Lenovo 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:9ca0 
  Sound Server: ALSA v: k5.4.64-1-MANJARO 
Network:
  Device-1: Intel Ethernet I218-V vendor: Lenovo driver: e1000e v: 3.2.6-k 
  port: 3080 bus ID: 00:19.0 chip ID: 8086:15a3 
  IF: enp0s25 state: down mac: <filter> 
  Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel port: efa0 
  bus ID: 03:00.0 chip ID: 8086:095b 
  IF: wlp3s0 state: up mac: <filter> 
  IF-ID-1: br-5a3bf264ca4c state: down mac: <filter> 
  IF-ID-2: br-a00b854a1782 state: down mac: <filter> 
  IF-ID-3: docker0 state: down mac: <filter> 
Drives:
  Local Storage: total: 119.24 GiB used: 93.15 GiB (78.1%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda vendor: Samsung model: MZ7LN128HCHP-000L1 size: 119.24 GiB 
  block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
  rev: 3L0Q scheme: MBR 
Partition:
  ID-1: / raw size: 110.44 GiB size: 108.21 GiB (97.98%) 
  used: 93.15 GiB (86.1%) fs: ext4 dev: /dev/sda1 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 45.0 C mobo: 0.0 C 
  Fan Speeds (RPM): cpu: 2570 
Info:
  Processes: 228 Uptime: 3m Memory: 7.48 GiB used: 2.71 GiB (36.2%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: pacman: 1510 lib: 393 
  Shell: Bash v: 5.0.18 running in: tilix inxi: 3.1.05 
~ $ sudo dmesg | grep blue
[    3.161117] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[   12.331905] audit: type=1130 audit(1601057343.045:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   42.358460] audit: type=1131 audit(1601057373.072:125): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   42.962484] audit: type=1130 audit(1601057373.675:126): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   72.718651] audit: type=1131 audit(1601057403.734:133): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=blueman-mechanism comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Thank you for the welcome and the info! I hope that my additions provide enough information for some assistance. I love Manjaro and I think this is the only snag.

For some reason your Bluetooth adapter isn’t being detected. I imagine it’s part of the Intel chipset.

What’s the output of lsusb?

~ $  lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp. Integrated Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 04f2:b449 Chicony Electronics Co., Ltd Integrated Camera
Bus 002 Device 006: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It exists!

What about:

sudo dmesg | grep -i bluetooth

I see you’re using the 5.4 LTS kernel. Have you tried 5.8?

~ $ sudo dmesg | grep -i bluetooth
[    3.752402] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked

I have not tried 5.8 kernel! I’ll give it a go.

Just tried 5.8. Same error behavior.

Howdy!

Try the following command! sudo pacman -S bluez bluez-libs gnome-bluetooth --noconfirm && sudo systemctl enable bluetooth

Have a wonderful day!

Hey! I gave it a shot and I get the same error defined above

Hi, does:

bluetoothctl
list

indicate that no adapters are found?

(My motherboard has the Intel AX200 chipset and its bluetooth module made me temporarily doubt reality until I found [Solved] No bluetooth from AX200 / Kernel & Hardware / Arch Linux Forums and acquired a usb bluetooth adapter)

Hi Clark,

I was looking through your issue on the Thinkpad T450 using bluetooth to connect to devices. I also have a T450 and though I can connect to my bluetooth headphones. My Manjaro Gnome install is about 1.5 weeks old with all patches.

I won’t say things are perfect because I am diagnosing the following issues before I file my own post:

  • Switch devices seems to be flaky (e.g. the Edifier Headphones I have will sometimes connect in a headset mode and not stereo hifi).
  • Youtube videos will suddenly freeze in full screen mode in Firefox. Come out of Full screen and video will continue to play.

That being said I noticed your T450 bios has not been updated from the original 2015. I recommend you update this first:

https://support.lenovo.com/ca/en/downloads/ds102109

I will keep you in the loop as I figure my way through the issues. Note that I remember having some similar issues with bluetooth with my T430s and x230 on some Manjaro builds. So I totally get the fustrations you must be feeling when you have a laptop from 2015.

My Laptop Details:

System:
  Kernel: 5.4.67-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.4-x86_64 
  root=UUID=913cf2e6-0ad6-4897-ac14-92ec4ba23a9a rw quiet udev.log_priority=3 
  Desktop: GNOME 3.36.6 tk: GTK 3.24.23 wm: gnome-shell dm: GDM 3.36.3 
  Distro: Manjaro Linux 
Machine:
  Type: Laptop System: LENOVO product: 20BV0064US v: ThinkPad T450 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: LENOVO model: 20BV0064US v: SDK0J40705 WIN serial: <filter> 
  UEFI: LENOVO v: JBET73WW (1.37 ) date: 08/14/2019

Hey Kagetora!

Thanks so much for the heads up about the BIOS! It’ll be my first time updating something like that. I don’t know if it’s unfortunate, yet I’m only running Manjaro so it’s unlikely that it’ll be easy.

I’ll take this issue with t450 and lenovo to keep track of these types of things.

On another note, I also have this problem:

Youtube videos will suddenly freeze in full screen mode in Firefox.

However, it is for any HTML5 video player.

1 Like

Hey Krill!

~ $ bluetoothctl
Waiting to connect to bluetoothd...

It hangs on that. Once upon a time it worked via the bluetoothctl however, it doesn’t seem like it.

EDIT: Adapter sounds like a good idea; although not preferable. We due do it exists yet aren’t sure exactly why it’s not connect.

I filed the Firefox Video bug here:

https://bugzilla.mozilla.org/show_bug.cgi?id=1671069

@krill @clarkkozak

So what I was reading on the Arch forum is some people are indicating that PulseAudio got broken on the latest release (which is causing Bluetooth to not connect dependably). The person in the below post downgraded their packages.

https://bbs.archlinux.org/viewtopic.php?id=259757

In my testing I did use the ‘bluetoothctl’ to connect to my headphones. I also issued the command to trust the device from command line. After this sound work correctly. But then after I reboot the laptop and try to connect to same headphones via Gnome Bluetooth controls it fails to connect again.

So if this is a regression with Pulse Audio, I’m trying to figure out whether there is a patch coming to Arch.

@kagetora13

How can I test this? This is my current version:

~ $ pulseaudio --version
pulseaudio 13.0

Is version 13.0 the breaking change?

Howdy!

Can you please try to follow this guide? :upside_down_face:

Hi Clark,

I’m also on version version 13 of Pulseaudio (so assuming this is part of the problem).

To be 100% honest I just switch this month from my Thinkpad x230\T430s (3 years on Manjaro) to the T450 and T450s as my daily drivers. So when I read through the thread in ([DOWNGRADED] Latest updates broke Bluetooth / Kernel & Hardware / Arch Linux Forums) I wonder if other updates to software are contribute the bad bluetooth behavior.

So perhaps what we should be looking for is whether an official bug has been filed on this issue?