[Pkg-bluetooth-maintainers] Bug#755274: Bug#755274: bluez: BT adapter isn't powered on at boot

[Andriy Martynets]

On Sat, 26 Jul 2014 04:52:49 +0900
Nobuhiro Iwamatsu <iwamatsu at nigauri.org> wrote:

Dear Nobuhiro,
Thanks!

Using of the udev rule is reasonable as this activates any BT adapter
as soon as it is plugged in. Maintaining this via an init script works
fine in majority of cases but not in all. As the script runs once it
will not cover cases when the adapter is hot plugged later.

Reverting this back will solve the bug as will make the package working
fine.

To improve the package by adding the udev rule you have to make the
hciconfig tool available from the rootfs.

Thank you again and best regards,
Andriy

> Hi,
> 
> Thanks for your report.
> 
> 2014-07-19 22:20 GMT+09:00 Andriy Martynets <martynets at volia.ua>:
> > Package: bluez
> > Version: 5.21-1
> > Severity: serious
> > Justification: Policy 9.1.1
> >
> > Dear Maintainer,
> > The issue appeared after upgrade to version 5.21.
> > The udev rule 50-bluetooth-hci-auto-poweron.rules tries to
> > run /usr/bin/hciconfig tool. This rule is executed at early stage
> > of boot process (/etc/rcS.d/S02udev) when /usr is mounted later
> > (/etc/rcS.d/S09mountall.sh). In my understanding this tool must be
> > installed in /sbin directory as one needed at boot time.
> > Alternatively this must be managed somehow at later stage (e.g.
> > 'udevadm trigger --verbose --action=add --subsystem-match=bluetooth
> > --sysname-match=hci*' command in /etc/init.d/bluetooth)
> >
> 
> I see.
> I enabled the hciX in bluetooth.init in earlier versions.
> I  will revert this and remove 50-bluetooth-hci-auto-poweron.rules
> from bluez package
> 
> > I tried the mentioned above udevadm command and it helped. See
> > modified file below. It also contains alterations to fix bug
> > #754830.
> >
> > Best regards,
> > Andriy
> >
> 
> 
> Best regards,
>   Nobuhiro
>