Comment 6 for bug 1565940

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?