touch-packages team mailing list archive

[JPTTEST <j-p-t@xxxxxxx>]

Another log using different BT-dongle on host.

** Attachment added: "bluetooth2.log"
   https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1342568/+attachment/4153834/+files/bluetooth2.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1342568

Title:
  bluetooth connect fails

Status in “bluez” package in Ubuntu:
  New

Bug description:
  I want to connect to a BT-serial adapter. Always get the error
  "Unknown command complete for opcode 37".

  If I supply the correct pin, connection is reported successful, but
  the device immediately disappears.

  I tried three different host BT hardware and two different PCs. always
  the same.

  Kubuntu 14.04
  Bluez-4.101-ubuntu13

  syslog: First with correct pin, second using wrong pin:

  bluetoothd[1107]: Discovery session 0x7f66d5221040 with :1.117 activated
  bluetoothd[1107]: Unknown command complete for opcode 37
  bluetoothd[1107]: Stopping discovery

  bluetoothd[1107]: Discovery session 0x7f66d52209a0 with :1.118 activated
  bluetoothd[1107]: Unknown command complete for opcode 37
  bluetoothd[1107]: Stopping discovery
  bluetoothd[1107]: hci0: Cancel Pair Device (0x001a) failed: Invalid Parameters (0x0d) 

  How do I enable more detailed logging?

  I am quite sure this is no duplicate of those BT-suspend bugs. Because
  it always fails and the rfkill workaround doesn't help.

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