The ubuntu-system-settings and indicator-bluetooth branches I've linked
here attempt to handle things more gracefully whenever indicator-
bluetooth can't work with /dev/rfkill -- it attempts to fall back to
just calling org.bluez.Adapter::SetProperties("Powered", on/off)
This is an improvement; unfortunately, it doesn't seem to be a complete
fix yet as powering on/off on the desktop is unreliable in the latest
nightlies, even when using bluez' command-line utilities to power off &
on again. I've filed that separate issue as bug #1238672
** Also affects: ubuntu-system-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) => Charles Kerr (charlesk)
** Changed in: indicator-bluetooth
Assignee: (unassigned) => Charles Kerr (charlesk)
** Branch linked: lp:~charlesk/ubuntu-system-settings/lp-1236249
** Branch linked: lp:~charlesk/indicator-bluetooth/lp-1236249
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236249
Title:
unity8 crashed with SIGSEGV in UnityMenuModelPrivate::itemState()
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1236249/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
