After a reboot headset does not autoconnect

[Takkat]

After a reboot my headset always is `disconnected' until connected manually by using the gnome-bluetooth panel applet.

How to reproduce

- Pair a Bluetooth headset and connect it sucessfully
- Switch off the device / or unplug the USB adapter
- Switch on the device / or plug in the USB adapter
- Observe that the headset is auto-connected as expected
- Reboot the computer (with plugged in USB adapter and headset turned on)
- Device is recognized but in `disconnected' state

What is expected

- Headsets should auto-connect after a reboot

Additional information: uncommenting `AutoConnect=true' in audio.conf does not make a difference.

Ubuntu Precise am64 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
bluez 4.98-2ubuntu7

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Sat May 5 21:36:26 2012
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Shuttle Inc SK22V10
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=8391913e-6b04-4f78-8f4a-38417283dfc1 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to precise on 2012-04-25 (10 days ago)
dmi.bios.date: 08/04/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: FX22V10
dmi.board.vendor: Shuttle Inc
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/04/2008:svnShuttleInc:pnSK22V10:pvr:rvnShuttleInc:rnFX22V10:rvr:cvn:ct3:cvr:
dmi.product.name: SK22V10
dmi.sys.vendor: Shuttle Inc
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:19:15:49:E2:75 ACL MTU: 1017:8 SCO MTU: 64:8
  UP RUNNING PSCAN
  RX bytes:820 acl:0 sco:0 events:31 errors:0
  TX bytes:385 acl:0 sco:0 commands:30 errors:0
mtime.conffile..etc.bluetooth.audio.conf: 2012-05-05T13:11:39.571872
rfkill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

[Takkat (takkat-nebuk)]

Autoconnecting operates as expected when the external device is powered on later, i.e. after a reboot completed. If the device was already powered on we need a signal (e.g. `Play') from the device to trigger autoconnection.

This indicates that the scanning and autoconnecting features of Bluez are fully operational. There is no bug here.