Found a dmesg output from the other bug; I think this is likely a strong hint towards the actual problem:
[ 6135.609315] Bluetooth: hci0 reading Intel fw version command failed (-110) [ 6137.610607] Bluetooth: hci0 command 0x0c03 tx timeout [ 6145.595944] Bluetooth: hci0 sending initial HCI reset command failed (-110) As above, this looks to me like the bluetooth device isn't done initializing by the time bluez tries to talk to it. -- 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
