** Summary changed:
- Can you buy Ambien without a script in Miami?
+ Bluetooth cannot be activated on several devices
** Description changed:
Using RC proposed 04/01/2016 bluetooth cannot be enabled.
-
- https://usapillspharma.com
Tested on a nexus 7.
Expected behavior:
Bluetooth
** Changed in: indicator-bluetooth (Ubuntu)
Assignee: Rodney Dawes (dobey) => (unassigned)
--
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/1530807
Title:
B
Reopening for workitem found by dobey to see if
https://code.launchpad.net/~morphis/indicator-bluetooth/fix-
lp1530807/+merge/290022 should still be landed
** Changed in: indicator-bluetooth (Ubuntu)
Status: Fix Committed => Triaged
** Changed in: indicator-bluetooth (Ubuntu)
Assignee
** Changed in: indicator-bluetooth (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: canonical-pocket-desktop
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator
I think it will be helpful to have a short new bug for this discussion,
so I've opened: bug #1587366. Please continue the discussion there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https:/
Hello all,
Using ths DUT at least 20 minutes, then trying to turn on the BT. DUT
cannot turning on by itself, user need to reboot the DUT to be able to
connect any BT device.
Fw: Ubuntu 15.04 (r10)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Summary changed:
- [FHD] Bluetooth cannot be activated on several devices
+ Bluetooth cannot be activated on several devices
--
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.launc
Maybe some of the issues here are a duplicate of bug #1546137 ?
--
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/1530807
Title:
Bluetooth cannot be activated on
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
--
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/1530807
Title:
Bluetooth
** Changed in: avila
Milestone: ww04-2016 => ww06-2016
--
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/1530807
Title:
Bluetooth cannot be activated on sever
(which worked for me on my frieza device -and seems to fix this bug)
--
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/1530807
Title:
Bluetooth cannot be activate
This in silo 79
--
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/1530807
Title:
Bluetooth cannot be activated on several devices
Status in The Avila project:
Is the linked branch believed to be a fix, or simply part of the puzzle?
--
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/1530807
Title:
Bluetooth cannot be acti
** Branch linked: lp:~charlesk/indicator-bluetooth/lp-1530807-watch-
bluez-owner-on-bus
--
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/1530807
Title:
Bluetooth
BlueZ will react either on the "Powered" property of its
org.bluez.Adapter1 interface being switch (false/true) or the bluetooth
rfkill being changed. If none of both happen the Bluetooth power status
will not change and the device will be kept discoverable if the
"Discoverable" property was set to
My bq 4.5 does not seem to have this problem in normal usage, so here's
how I managed to reproduce it:
1) disable autostart of the bluetooth daemon:
$ echo "manual" | sudo tee /etc/init/bluetooth.override
2) reboot your phone
3) wait until everything is loaded, then run:
$ sudo start bluetooth
** Changed in: avila
Status: Confirmed => 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/1530807
Title:
Bluetooth cannot be activated on sev
I think there is an indicator-datetime issue herer wrt the on/off toggle
in the indicator, but there is also a separate issue with the
Discoverable / Not Discoverable status being shown in system-settings.
indicator-bluetooth doesn't advertise that state; system-settings is
getting that from talkin
** Changed in: indicator-bluetooth (Ubuntu)
Status: Confirmed => 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/1530807
Title:
Bluetooth can
** Changed in: avila
Milestone: ww06-2016 => ww04-2016
--
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/1530807
Title:
Bluetooth cannot be activated on sever
** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => ww04-2016
--
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/1530807
Title:
Bluetooth can
** Changed in: avila
Assignee: (unassigned) => Alejandro J. Cura (alecu)
--
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/1530807
Title:
Bluetooth cannot be
** Tags added: qa-frieza
--
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/1530807
Title:
Bluetooth cannot be activated on several devices
Status in The Avila pr
** Changed in: indicator-bluetooth (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/1530807
Title:
Bluetooth cannot be a
Additional OEM bug that's probably a dupe: bug #1544084
--
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/1530807
Title:
Bluetooth cannot be activated on several
This also occurs on frieza, OEM bug: #1534318
** Changed in: canonical-devices-system-image
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
26 matches
Mail list logo
