← Back to team overview

kernel-packages team mailing list archive

[Bug 1312032] Re: [systemd] does not start at boot, service not enabled

 

This bug was fixed in the package bluez - 4.101-0ubuntu14

---------------
bluez (4.101-0ubuntu14) utopic; urgency=medium

  * Remove obsolete and unused udev helpers for bluetoothd and hid2hci.
  * Enable systemd service file on installation. This hooks up the service in
    bluetooth.target which is activated by systemd when bluetooth hardware is
    attached. (Closes: #729808, LP: #1312032)
    - Add Build-Depends on dh-systemd.
    - Bump Build-Depends on cdbs to (>= 0.4.122) to get dh-systemd support.
    - Workaround a bug in cdbs, which doesn't run dh_install and dh_systemd
      the correct order, by pointing dh_systemd_enable and dh_systemd_start at
      the uninstalled service file. See #715504 for details.
    - Taken from Debian's 4.101-4.1, thanks Michael Biebl!
 -- Martin Pitt <martin.pitt@xxxxxxxxxx>   Thu, 24 Apr 2014 11:40:37 +0200

** Changed in: bluez (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
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/1312032

Title:
  [systemd] does not start at boot, service not enabled

Status in “bluez” package in Ubuntu:
  Fix Released

Bug description:
  bluetooth.service does not install itself. The Debian package has a
  workaround for this:
  http://packages.qa.debian.org/b/bluez/news/20140306T074915Z.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1312032/+subscriptions


References