I'm pretty sure this has to do with the ordering of the bluetooth-touch,
bluetooth (bluez) and urfkill jobs. IIRC bluetooth-touch jobs do some
firmware tweaks that can't work if the device isn't available or rfkill
blocked, but we also need to be very sure that the radios are off all
the while flight mode is enabled and bluetooth isn't, since this is part
of regulatory requirements.
Since it's probably changes in the upstart jobs and only that, I'm
adding a task for lxc-android-config. Let's keep the urfkill task in
case there is any work needed there, but it seems to me like the logic
in urfkill is already correct.
** Changed in: urfkill (Ubuntu)
Status: Confirmed => Triaged
** Changed in: urfkill (Ubuntu)
Importance: Undecided => High
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc-android-config (Ubuntu)
Importance: Undecided => High
** Changed in: lxc-android-config (Ubuntu)
Status: New => Triaged
** Changed in: lxc-android-config (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421249
Title:
bluetooth can not be enabled sometimes (when booting with flight mode
on being one case)
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421249/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
