kernel-packages team mailing list archive

[Alfonso Sanchez-Beato <alfonso.sanchez-beato@xxxxxxxxxxxxx>]

I have been trying to reproduce this by switching on/off bluetooth from
the indicator and from system setting several times, but no luck yet.

While doing this I tried to connect a BT headset after each few tries,
successfully. I also left the tablet aside for a few minutes without BT,
then was able to turn it on successfully too.

Were there any files in /var/crash/ when this happened? Could somebody
attach syslog after reproducing this?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1587366

Title:
  On cooler devices, BT sometimes cannot be enabled

Status in The Avila project:
  New
Status in Canonical System Image:
  New
Status in cooler:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
   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)

  Tested on a cooler (M10 HD)

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior:
  Bluetooth slider is moved to on
  Activity spinners appear
  Bluetooth slider moves to off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1587366/+subscriptions