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 <konrad.zapalow...@canonical.com> 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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1744806
Title:
Bluetooth is turned off at boot with latest update (bluez
5.37-0ubuntu5.2)
Status in bluez package in Ubuntu:
Triaged
Bug description:
With latest update, BLUEZ is now off right after boot, as opposed to
previous behaviour that was on/off depending on last setting.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jan 22 16:08:20 2018
InstallationDate: Installed on 2017-09-29 (115 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 04f2:b59d Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System76 Lemur
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash
resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/17/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Tag 12345
dmi.board.name: Lemur
dmi.board.vendor: System76
dmi.board.version: lemu7
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Lemur
dmi.product.version: lemu7
dmi.sys.vendor: System76
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: AC:ED:5C:F6:32:44 ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:667 acl:0 sco:0 events:38 errors:0
TX bytes:405 acl:0 sco:0 commands:38 errors:0
mtime.conffile..etc.bluetooth.input.conf: 2017-12-06T11:16:58.937870
mtime.conffile..etc.bluetooth.main.conf: 2018-01-18T18:34:20.102879
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1744806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
