kernel-packages team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

There is absolutely no reason why delaying bluez from starting should
affect S3/S4 or killswitches in any normal case, especially not in a
relation with dbus, for which the connection is only established on
startup.

There *is* a chance where bluetooth would start and not have dbus
available, but in this case it would fail immediately on startup, which
does not appear to be the issue at hand. That said, since it's a
possibility I have a test patch ready.

Please attach a full copy of /var/log/syslog to this bug report so we
can see all the messages from bluez and from the kernel bluetooth
subsystem. It really seems to me like this is an issue caused by an
incomplete initialization of the bluetooth device by the time bluez
starts, which is something that really should get fixed in the kernel
itself rather than as a workaround in bluez.

** Changed in: bluez (Ubuntu)
       Status: New => Incomplete

** Changed in: bluez (Ubuntu Precise)
       Status: New => Incomplete

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: bluez (Ubuntu)
     Assignee: Canonical Desktop Team (canonical-desktop-team) => Mathieu Trudel-Lapierre (mathieu-tl)

-- 
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:
  New
Status in “bluez” source package in Precise:
  Incomplete
Status in “linux” source package in Precise:
  New

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