I think the udev flag on bluez should install rules files which automatically run hcitool hci* up when an interface is available. Otherwise the user has to write such a file themselves.
Doesn't bluetooth service do this already? https://wiki.gentoo.org/wiki/Bluetooth#Service
It did not for me.
It is a different bug then. You shouldn't need to manually (or with a workaround as you suggest) run hcitool If still suffering that issue with latest version, please report the problem directly to upstream -> http://www.bluez.org/contact/ (I would opt for IRC or mailing list)
The initial bug description was wrong, this concerns hciconfig hci* up NOT hcitool. And hcitool seems to have no knowledge of any interface (and neither does bluez) if the interface is not brought up before that. Sorry for the confusion. Re-opening unless you insist it be closed.
Please report it to upstream directly
