** 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:
** 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:
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)
** 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
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.
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.
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:
** 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
(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
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
** 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:
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
** 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
** 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
** 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
** 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
** 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
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
** 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
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: 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
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.
** Also affects: avila
Importance: Undecided
Status: New
** Summary changed:
- Bluetooth cannot be activated on Nexus 7
+ Bluetooth cannot be activated on several devices
** Changed in: avila
Status: New => Confirmed
** Changed in: avila
Importance: Undecided => Critical
Definitely happens on mako using the -pd image (r127) which renders it
completely useless as a -pd image.
** Changed in: canonical-pocket-desktop
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I confirm that this bug also happens in mako.
current build number: 355
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
Pat, this problem also affects the nexus 4 I believe.
--
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 Nexus 7
** Summary changed:
- Bluetooth cannot be activated.
+ Bluetooth cannot be activated on Nexus 7
--
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:
I'm seeing similar buggy behavior with the indicator on a Xenial desktop
with bluez 5.36 and indicator-bluetooth 0.0.6+15.10.20150929-0ubuntu1
installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
some more information: Bluetooth only appears being off in the indicator
and the settings. It is, in fact on and working just fine.
This screenshot was taken while a Bluetooth keyboard was connected and
functional: http://i.imgur.com/EIUnG9n.png
Note the hciconfig output in the terminal. It
I've experienced this before and was fixed I think when bluez5 landed.
However I experience it again sometimes in the recent rc-proposed images.
A couple of reboots fix the issue though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-bluetooth (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
Adding my experience to comment #12, reboots will sometimes fix the
issue, but anecdotally I'd estimate the frequency at 10%. (i.e. one in
ten reboots clears it.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: canonical-pocket-desktop
Importance: Undecided
Status: New
** Changed in: indicator-bluetooth (Ubuntu)
Importance: Undecided => High
** Changed in: canonical-pocket-desktop
Importance: Undecided => High
** Changed in: canonical-devices-system-image
fwiw, my current workflow to workaround this is to log onto the device shell
and "restart indicator-bluetooth"
the list of available devices always instantly appears.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I can confirm that the Nexus 4 isn't affected. Seems isolated to the
Nexus 7.
--
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
Problem persists with r334
** Attachment added: "screenshot20160109_140631775.png"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1530807/+attachment/4546889/+files/screenshot20160109_140631775.png
--
You received this bug notification because you are a member of Ubuntu
I can confirm this affects rc proposed r332.
--
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.
Status in Canonical
Cannot reproduce on any other devices, could be specific to the N7 or
the current state of the specific device.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
** Changed in: indicator-bluetooth (Ubuntu)
Assignee: (unassigned) => Charles Kerr (charlesk)
--
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:
The images show that in neither case is the Bluetooth indicator shown in
the top panel
** Also affects: indicator-bluetooth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in:
I am (I think) able to observe the slider behaviour referenced in the
bug on my N7, running r329. My device initially discoverable, even when
the slider reverts to "off" by itself. Shortly after (maybe a few
minutes later), the N7 is no longer discoverable and turning the slider
back to "on" has
44 matches
Mail list logo
