kernel-packages team mailing list archive

[Dave Morley <davmor2@xxxxxxxxxxxxx>]

Public bug reported:

STEPS:
1. Flash a fresh image of vivid on a krillin device
2. Check if bluetooth is on
3. Reboot

EXPECTED:
I always expect bluetooth to be on

ACTUAL:
Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how ever it wouldn't connect to anything.

** Affects: bluez (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1432788

Title:
  Race in vivid means sometimes bluetooth is no available

Status in bluez package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Flash a fresh image of vivid on a krillin device
  2. Check if bluetooth is on
  3. Reboot

  EXPECTED:
  I always expect bluetooth to be on

  ACTUAL:
  Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how ever it wouldn't connect to anything.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1432788/+subscriptions