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.p...@ubuntu.com> Mon, 03 Nov 2014 07:47:56 +0100
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387282
Title:
bluetooth rfkill status not synced between upstart and systemd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1387282/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
