Steps: - Adjust our udev rules to call path_id for rfkill devices also under upstart - Adjust rfkill upstart jobs to call lib/systemd/systemd-rfkill load/save, so that both init systems use the same state files. These include the path_id under systemd, so that needs to be consistently available.
** Also affects: rfkill (Ubuntu) Importance: Undecided Status: New ** Changed in: rfkill (Ubuntu) Status: New => Triaged ** Changed in: rfkill (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- 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 devices are missing when booting with systemd Status in “rfkill” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp