It appears this bug is due to a proposed change:
bluez (5.37-0ubuntu5.2) xenial; urgency=medium
[Simon Fels]
[Guilhem Lettron]
[Cyrus Lien]
* debian/main.conf:
- Set AutoEnable parameter to true.
(LP: #1510570)
* debian/50-bluetooth-hci-auto-poweron.rules:
- Get rid of legacy udev rule to power on bluetooth controllers on
startup. Using hciconfig for that is the legacy way and will lead
to different problems as the kernel side stack wont initialize
all needed subsystems when used. BlueZ introduced a replacement
for this with 5.36 which basically tells the bluetoothd through
a config option to turn on all found Bluetooth controllers by
default. With changing this there should be no change in terms
of functionality.
(LP: #1510570)
-- Konrad Zapałowicz <[email protected]> Tue, 14 Nov
2017 14:07:37 +0100
You might find more information in bug 1510570, but this is still a bug
by the sounds of it.
** Tags added: regression-proposed
** Changed in: bluez (Ubuntu)
Importance: Undecided => Medium
** Changed in: bluez (Ubuntu)
Status: New => Triaged
** Summary changed:
- Bluetooth is turned off at boot with latest update
+ Bluetooth is turned off at boot with latest update (bluez 5.37-0ubuntu5.2)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744806
Title:
Bluetooth is turned off at boot with latest update (bluez
5.37-0ubuntu5.2)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1744806/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
