So I think this bug should be split into two different bugs.
First, the original reporter filed this on an x86 machine running
Desktop, not Touch. As urfkill is still not used on the Desktop as of
the latest utopic images, I'm splitting this into a urfkill bug for the
problems described by myself and Renato on phones, and a rfkill bug for
the desktop issue ( although this could actually be a driver/hardware-
specific bug vs. a bug in the rfkill package ).
Bug #1376063 has been created to track the urfkill problem seen with the
phone images and the urfkill task in this bug marked Invalid. All
phone-related tags have been copied to the new bug and removed from this
bug.
** Tags removed: beta qa-daily-testing rtm14 touch-2014-10-09
** Changed in: urfkill (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296114
Title:
Bluetooth is always enabled after reboot even if it was disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
