`rfkill unblock bluetooth` cannot enable bluetooth

I can disable bluetooth with rfkill block bluetooth but cannot enable it with rfkill unblock bluetooth. I can enable it with Manjaro settings though.
Here’s the output of rfkill list | grep -A 2 bluetooth after running rfkill block bluetooth :

0: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no

Here’s the output of rfkill list | grep -A 2 bluetooth after running rfkill unblock bluetooth :

0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

But bluetooth is not enabled at this time. Here’s the output after enabling it from KDE settings :

0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

Exactly the same. I’m unable to figure out what’s exactly happening. Please help.

inxi -Fazy

System:
  Kernel: 5.11.2-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.11-x86_64 
  root=UUID=fe64fafd-1c2a-4b55-846f-c264196ff166 rw nomce "acpi_osi=Windows 
  2018" quiet resume=UUID=4517ac81-4ac6-42a0-8e7a-a5870b5f98df 
  Desktop: KDE Plasma 5.21.2 tk: Qt 5.15.2 wm: kwin_x11 dm: GDM 3.38.2.1, SDDM 
  Distro: Manjaro Linux 
Machine:
  Type: Laptop System: HP product: HP Pavilion Laptop 14-bf1xx 
  v: Type1ProductConfigId serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: HP model: 83CE v: 59.38 serial: <filter> UEFI: Insyde v: F.31 
  date: 10/30/2017 
Battery:
  ID-1: BAT1 charge: 42.3 Wh condition: 42.3/42.3 Wh (100%) volts: 13.2/11.6 
  model: Hewlett-Packard PABAS0241231 type: Li-ion serial: <filter> 
  status: Full 
CPU:
  Info: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP 
  arch: Kaby Lake note: check family: 6 model-id: 8E (142) stepping: A (10) 
  microcode: E0 L2 cache: 8 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 32012 
  Speed: 838 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 838 2: 865 3: 875 
  4: 847 5: 847 6: 800 7: 800 8: 800 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported 
  Type: l1tf mitigation: PTE Inversion 
  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 UHD Graphics 620 vendor: Hewlett-Packard driver: i915 
  v: kernel bus ID: 00:02.0 chip ID: 8086:5917 class ID: 0300 
  Device-2: NVIDIA GM108M [GeForce 940MX] vendor: Hewlett-Packard 
  driver: nvidia v: 460.56 alternate: nouveau,nvidia_drm bus ID: 01:00.0 
  chip ID: 10de:134d class ID: 0302 
  Device-3: Chicony HP Wide Vision HD Camera type: USB driver: uvcvideo 
  bus ID: 1-5:4 chip ID: 04f2:b5d6 class ID: 0e02 
  Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: 
  loaded: modesetting,nvidia display ID: :0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 115 s-size: 424x238mm (16.7x9.4") 
  s-diag: 486mm (19.1") 
  Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 158 size: 309x173mm (12.2x6.8") 
  diag: 354mm (13.9") 
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.3.4 
  direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard 
  driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus ID: 00:1f.3 
  chip ID: 8086:9d71 class ID: 0403 
  Sound Server: ALSA v: k5.11.2-1-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Hewlett-Packard driver: r8168 v: 8.048.03-NAPI modules: r8169 
  port: 3000 bus ID: 02:00.0 chip ID: 10ec:8168 class ID: 0200 
  IF: eno1 state: down mac: <filter> 
  Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel port: 3000 
  bus ID: 03:00.0 chip ID: 8086:095a class ID: 0280 
  IF: wlo1 state: up mac: <filter> 
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 
  bus ID: 1-4:3 chip ID: 8087:0a2a class ID: e001 
  Message: Required tool hciconfig not installed. Check --recommends 
Drives:
  Local Storage: total: 1.03 TiB used: 581.84 GiB (55.4%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172 
  size: 931.51 GiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  rotation: 5400 rpm serial: <filter> rev: RSM7 scheme: GPT 
  ID-2: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SD8SN8U-128G-1006 
  size: 119.24 GiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  rotation: SSD serial: <filter> rev: 0006 scheme: GPT 
Partition:
  ID-1: / raw size: 50 GiB size: 48.72 GiB (97.43%) used: 26.37 GiB (54.1%) 
  fs: ext4 dev: /dev/sdb5 maj-min: 8:21 
  ID-2: /boot/efi raw size: 277 MiB size: 276.4 MiB (99.80%) 
  used: 280 KiB (0.1%) fs: vfat dev: /dev/sdb1 maj-min: 8:17 
  ID-3: /home raw size: 60.87 GiB size: 59.67 GiB (98.02%) 
  used: 31.19 GiB (52.3%) fs: ext4 dev: /dev/sdb2 maj-min: 8:18 
Swap:
  Kernel: swappiness: 5 (default 60) cache pressure: 50 (default 100) 
  ID-1: swap-1 type: partition size: 8.1 GiB used: 8.2 MiB (0.1%) priority: -2 
  dev: /dev/sdb3 maj-min: 8:19 
Sensors:
  System Temperatures: cpu: 46.0 C mobo: 29.8 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 349 Uptime: 31m wakeups: 2 Memory: 7.69 GiB 
  used: 5.34 GiB (69.4%) Init: systemd v: 247 Compilers: gcc: 10.2.0 
  Packages: 2097 pacman: 2096 lib: 469 flatpak: 1 Shell: fish v: 3.1.2 
  running in: server inxi: 3.3.01 

In my understanding:
with:
rfkill unblock bluetooth
it can be unblocked
if it is blocked for some reason

… from being prevented to being enabled

unblocking it is not the same as enabling it
enabling is done through:
sudo systemctl enable bluetooth.service

… which can’t be done or which won’t be successful
if bluetooth is … (hard or soft) blocked

It used to work. I’m not sure exactly when it broke.
Anyway, sudo systemctl enable bluetooth.service doesn’t work for me either.

I don’t know then.
unblocking is just not the same or equivalent to enabling
and
successfully enabling it needs it to be … unblocked

sudo is not needed for systemctl commands

try using

systemctl status bluetooth.service

to see if the service is available

Yes, it’s running.

I found a workaround using bluetoothctl power <on/off>.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.