** Changed in: urfkill (Ubuntu)
Status: Invalid = Triaged
** Changed in: urfkill (Ubuntu)
Importance: Critical = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
I'm keeping this open because some fixes will still need to happen in
both rfkill and urfkill for this to work properly; just like there will
be at least the need to also start shipping urfkill by default on
desktop before this works better.
One of the issues is that rfkill ships scripts that
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
Confirmed on krillin RTM #72 with the urfkill changes currently in RTM
silo-024.
That said, it's not currently InProgress by either myself or Mathieu,
thus 2014-10-02 is over-optimistic. As such I'm pushing to the
following weeks' milestone.
** Changed in: urfkill (Ubuntu)
Status: In
** Tags added: touch-2014-10-02
** Changed in: urfkill (Ubuntu)
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1296114
Title:
** Changed in: urfkill (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1296114
Title:
Bluetooth is always enabled
** Tags added: beta qa-daily-testing rtm14
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1296114
Title:
Bluetooth is always enabled after reboot even if it
Just tried this on a recent image ( #183 ) on mako, and I can reproduce
it.
It looks like the bluetooth indicator doesn't talk to urfkill directly.
When I disable BT via the indicator, the rfkill state is indeed toggled,
as if I run 'rfkill list', it shows as soft-blocked.
--
You received this
8 matches
Mail list logo