[Bug 1387282] Re: bluetooth rfkill status not synced between upstart and systemd

2014-11-03 Thread Launchpad Bug Tracker
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

[Bug 1387282] Re: bluetooth rfkill status not synced between upstart and systemd

2014-11-03 Thread Launchpad Bug Tracker
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

[Bug 1387282] Re: bluetooth rfkill status not synced between upstart and systemd

2014-11-02 Thread Martin Pitt
** Summary changed: - bluetooth devices are missing when booting with systemd + bluetooth rfkill status not synced between upstart and systemd ** Changed in: rfkill (Ubuntu) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1387282] Re: bluetooth rfkill status not synced between upstart and systemd

2014-11-02 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/rfkill/vivid-proposed -- 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