Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

hcitool/hciconfig are now deprecated in upstream bluez

See original GitHub issue
[parker@satellite ~]$ sudo ds4drv 
[error][daemon] 'hcitool' could not be found, make sure you have bluez-utils installed.

Under the first notes section

There is a compat package but it’s only on the AUR so not everybody will have access to it.

Issue Analytics

  • State:open
  • Created 7 years ago
  • Reactions:2
  • Comments:18

github_iconTop GitHub Comments

BlackLightcommented, Aug 6, 2020

Somebody decided to deprecate the executables that have been used for years by tons of devs and scripts to interact with the bluetooth stack without providing any viable alternative (“experiment with the dbus interaction to emulate what bluetoothctl does”, “pipe a bunch of echos to bluetoothctl”, “btmgmt is the new hciconfig - oh sorry, it’s not going to be official yet”).

That’s probably one of the dumbest things a software developer can do. Would it have been that expensive to keep the old executables until a new, stable way to handle bluetooth scripting with the new ones was out? You CAN’T deprecate something unless the alternative allows you to do exactly the same things you were able to do with the previous implementation! And the documentation is totally absent too - lots of pages still reference the hci* tools, and some (like the Arch Linux wiki) are themselves confused on what’s the right way to do things now. Most of all, users haven’t yet received an answer to a simple question: why were they deprecated in the first place?

I hope the guys at Bluez will soon recover from their unjustified booze and provide us with new reliable ways to do what we used to do until a year ago.

parkerlreedcommented, Mar 9, 2017

Just putting this here as reference for the dbus locations

$ qdbus --system org.bluez /org/bluez/hci0 org.bluez.Adapter1.Powered 

That same value has read/write enabled on it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

FS#53110 : no hcitool/hciconfig tools in bluez-utils 5.44-1 - Arch Linux
Additional comments about closing: Several tools are now declared deprecated and got removed by upstream decision. See also commit msg.
Read more >
hcitool/hciconfig are now deprecated in upstream bluez
hcitool/hciconfig are now deprecated in upstream bluez.
Read more >
phocean on Twitter: "and gattool is also among the victims ...
oO Deprecating very usefool utilities without any official replacement... #WTF hcitool/hciconfig are now deprecated in upstream bluez · Issue #123 ...
Read more >
Changes/BluetoothDeprecated - Fedora Project Wiki
There's a number of utilities in the upstream bluez bluetooth package that have long been deprecated with their functionality replaced by ...
Read more >
Package bluez-deprecated - man pages - ManKier
Bluetooth applications that have bee deprecated by upstream. They have been replaced by funcationality in the core bluetoothctl and will eventually be ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found