[Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

[Eric Ding]

I'm experiencing a similar issue on Thinkpad x220 running Linux Mint 18
(based on Ubuntu 16.04) with kernel 4.4.0-21.  In my case, rfkill
unblock needs to be called twice in order to fully enable (and soft
unblock) bluetooth:

# rfkill block bluetooth
# rfkill list bluetooth
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: yes
	Hard blocked: no
# rfkill unblock bluetooth
# rfkill list bluetooth
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
5: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no

(At this stage, Bluetooth appears to be on in the Mint Bluetooth
configuration dialog but can't see any devices).

# rfkill unblock bluetooth
# rfkill list bluetooth
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
5: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

(Now Bluetooth works fully as expected).

-- 
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1603715

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking and after
  suspend/resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1603715/+subscriptions