This bug was fixed in the package systemd - 215-5ubuntu2 --------------- systemd (215-5ubuntu2) vivid; urgency=medium
* Merge fixes from Debian: - Adjust timedated and hostnamed autopkgtests to current upstream version. - Replace our Debian hwdb.bin location patch with what got committed upstream. Run hwdb update with the new --usr option to keep current behaviour. - debian/README.Debian: Document how to debug boot or shutdown problems with the debug shell. (Closes: #766039) - Skip-99-systemd.rules-when-not-running-systemd-as-in.patch: Call path_id under all init systems, to get consistent ID_PATH attributes. This is required so that tools like systemd-rfkill can be used with SysVinit or upstart scripts, too. (LP: #1387282) -- Martin Pitt <martin.p...@ubuntu.com> Mon, 03 Nov 2014 07:15:38 +0100 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: rfkill (Ubuntu) Status: Fix Committed => Fix Released -- 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