net-wireless/bluez: install the btmgmt tool

[lukash]

The btmgmt tool is not installed by bluez. Recently it became necessary to power on the bluetooth, with kernels 4.1.6 and up the hciconfig tool no longer powers on the bluetooth correctly for LE devices to work (see http://www.spinics.net/lists/linux-bluetooth/msg64021.html).

I'm not entirely sure the patch is correct and is perhaps a version bump in place? Let me know and I'll fix it.

[kensington]

@pacho2

[pacho2]

Hi!

I am ok with the change, but I would make a revbump and add a commented line explaining the reasons for installing this. Once that is done, I won't have any problem with merging it

Thanks :)

[lukash]

Ok, I shall try :)

Although meanwhile, I've found out the btmgmt tool doesn't work as replacement for the hciconfig tool when powering up the adapter after suspend. See this thread in systemd ML: http://lists.freedesktop.org/archives/systemd-devel/2015-September/034419.html

Also as stated by Marcel Holtmann (bluez dev), btmgmt is a developer tool, which is why it isn't installed by default. I think it still may come handy, what is your opinion? In case you don't want developer tools installed, I'd wait how the discussion pans out with regards to this particular problem. So far it seems that even if it is going to have a reasonable solution, btmgmt won't be strictly necessary.

[pacho2]

It looks like finally no solution landed :(, but, personally, I prefer the systemd oneshot solution. On the other hand, for people not running systemd, they will probably still need the developer tools then, I am a bit unsure about what should we do :S

Is there any link to the bluez mailing list thread where maybe some more discussion has occurred?

Thanks

[lukash]

Don't worry :) I just haven't had much time and I was also waiting for two things:

You to express your opinion on whether we should install the btmgmt even though it's a development tool :)

And to get a reply to the thread I linked on systemd mailing list (didn't get any :().

Now (well, hopefully tomorrow) I'm planning to post a question to the bluez mailing list. So if you're unsure what to do, we can wait for that to pan out and decide later. If you'd like to install btmgmt anyway, I can whip up something tomorrow.

[pacho2]

I have just bumped bluez to 5.35 that is supposed to help with your issues:
This release contains bugfixes to areas such as GATT, OBEX, HoG and AVRCP. From now on bluetoothd will cache more information of remote GATT databases and thereby avoid unnecessary rediscovery of remote services.

A noteworthy new feature is the ability to configure bluetoothd to automatically enable (power on) all new adapters. One use of this is to replace unreliable “hciconfig hci0 up” commands that some distributions use in their init/udev scripts. The feature can be enabled by having AutoEnable=true under the [Policy] section of /etc/bluetooth/main.conf.

[mgorny]

Is there anything left to do then? Please either update or close the pull request :-).

[pacho2]

Ah, sorry, I am still getting used to this workflow :)

@lukash Reading upstream mails, it looks like they are willing to try to fix the inner bug you are suffering on a different way and, then, I would opt for closing this as WONTFIX or, at least, not install that tool for now and see if it can be finally solved in the way upstream wants

[lukash]

@pacho2 Thanks! The AutoEnable option seems to be working fine.