kernel-packages team mailing list archive

[Andy Whitcroft <apw@xxxxxxxxxxxxx>]

By the looks of things this is a platform wherein the actual bluetooth
controller is powered off when the kill switch is turned on, and powered
up again when the switch is turned off.  Thus the controller is
initialising when the event is emitted, which starts the bluez which is
getting there before it is ready to be used.  The fact that a very small
timeout before starting it in the upstart job is sufficient to always
fix this seem indicative of this.  The logical first step would be to
make the open for the device in userspace detect the open error and
pause and retry a couple of times.  Likely we are getting EAGAIN or
similar.

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

Title:
  Bluetooth doesn't work after S3/S4 or after turning bluetooth on/off
  several times by toggle key

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project precise series:
  Confirmed
Status in “bluez” package in Ubuntu:
  Incomplete
Status in “linux” package in Ubuntu:
  Incomplete
Status in “bluez” source package in Precise:
  Incomplete
Status in “linux” source package in Precise:
  Incomplete

Bug description:
  After S3/S4 or turning bluetooth on/off several times by toggle key,
  there are many error messages in dmesg. And sometime the bluetooth menu is incomplete.
  dmesg:
  [ 1117.356421] init: bluetooth main process (3848) terminated with status 1
  [ 1117.356506] init: bluetooth main process ended, respawning
  [ 1117.399989] init: bluetooth main process (3857) terminated with status 1
  [ 1117.400048] init: bluetooth main process ended, respawning

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