touch-packages team mailing list archive

[Launchpad Bug Tracker <1387282@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package rfkill - 0.5-1ubuntu2

---------------
rfkill (0.5-1ubuntu2) vivid; urgency=medium

  * Ensure that rfkill devices have ID_PATH attribute:
    - debian/control: Add dependency for systemd >= 215-5ubuntu2.
    - debian/rfkill.postinst: udev-trigger rfkill devices to ensure systemd
      215-5ubuntu2's adjusted 99-systemd.rules are applied on upgrade.
    - This upgrade fix needs to be kept until after Ubuntu 16.04 LTS.
  * debian/rfkill-{store,restore}.upstart: Use /lib/systemd/systemd-rfkill, to
    keep rfkill state between boots synchronized between upstart and systemd.
    (LP: #1387282)
 -- Martin Pitt <martin.pitt@xxxxxxxxxx>   Mon, 03 Nov 2014 07:47:56 +0100

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rfkill in Ubuntu.
https://bugs.launchpad.net/bugs/1387282

Title:
  bluetooth rfkill status not synced between upstart and systemd

Status in “rfkill” package in Ubuntu:
  Fix Released
Status in “systemd” package in Ubuntu:
  Fix Released

Bug description:
  I cannot use bluetooth devices while using systemd as the default init
  system.

  While going to gnome-control-center to check for bluetooth devices,
  all the bluetooth functionality is deactivated.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-8ubuntu8
  Uname: Linux 3.17.1-031701-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 29 17:43:44 2014
  InstallationDate: Installed on 2014-10-22 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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