Actually I realized that I had changed some lines on /etc/bluetooth/hcid.conf, if I use Ubuntu's default file.
I get the exact same errors on daemon log as the zdzichu (the bug submitter).
FWIW, I can always manually connect, and disconnect using hcitool:
# hcitool info 00:1D:25:B7:C2:C8 Requesting information ... BD Address: 00:1D:25:B7:C2:C8 Device Name: Samsung WEP300 LMP Version: 2.0 (0x3) LMP Subversion: 0xd57 Manufacturer: Cambridge Silicon Radio (10) Features: 0xff 0xfe 0x0b 0x00 0x08 0x08 0x00 0x00 <3-slot packets> <5-slot packets> <encryption> <slot offset> <timing accuracy> <role switch> <hold mode> <sniff mode> <RSSI> <channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme> <transparent SCO> <AFH cap. slave> <AFH cap. master>
# hcitool con Connections: < eSCO 00:1D:25:B7:C2:C8 handle 0 state 8 lm SLAVE
Actually I realized that I had changed some lines on /etc/bluetooth/ hcid.conf, if I use Ubuntu's default file.
I get the exact same errors on daemon log as the zdzichu (the bug submitter).
FWIW, I can always manually connect, and disconnect using hcitool:
# hcitool info 00:1D:25:B7:C2:C8
Manufacturer: Cambridge Silicon Radio (10)
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<transparent SCO> <AFH cap. slave> <AFH cap. master>
Requesting information ...
BD Address: 00:1D:25:B7:C2:C8
Device Name: Samsung WEP300
LMP Version: 2.0 (0x3) LMP Subversion: 0xd57
Features: 0xff 0xfe 0x0b 0x00 0x08 0x08 0x00 0x00
# hcitool con
Connections:
< eSCO 00:1D:25:B7:C2:C8 handle 0 state 8 lm SLAVE