I'm afraid that this is how the bluetoothctl is designed. This tool is a
command-line interface to the bluetoothd and requires it up and running.
It will not quit however when it is not running for a situations where
the daemon might come back online.
Ubuntu does not do anything special here, the bluetoothctl tool is
packaged as is from the upstream.
For Ubuntu this normally should not be a problem because a user is
expected to use {unity,gnome}-system-settings anyway to interact with BT
subsystem. Is there a particular use-case that is failing on this
behavior?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565940
Title:
bluetoothctl systematically hangs when there is no bluetooth hardware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
