Hi Andrew, On Mon, Mar 7, 2016 at 4:27 PM, Andrew - <hidefromkgb@xxxxxxxxx> wrote: >> I don't remember having any problems pairing the Designer Keyboard, how did you actually connected to it? > $ bluetoothctl > [NEW] Controller 00:08:CA:E7:CD:35 UX31E [default] > [NEW] Device E8:12:16:14:E0:20 Designer Mouse > [NEW] Device C1:C3:5B:2E:97:B9 Designer Keyboard > [bluetooth]# agent DisplayYesNo > Agent registered > [bluetooth]# default-agent > Default agent request successful > [bluetooth]# pair C1:C3:5B:2E:97:B9 > Attempting to pair with C1:C3:5B:2E:97:B9 > [CHG] Device C1:C3:5B:2E:97:B9 Connected: yes > [Designer Keyboard]# connect C1:C3:5B:2E:97:B9 > Attempting to connect to C1:C3:5B:2E:97:B9 > Connection successful > [bluetooth]# > > And that`s pretty much the end. The «Ready to connect» LED still > flashes and no input can be retrieved from the keyboard. > > dmesg shows its usual line: > [180261.398350] Bluetooth: SMP security requested but not available I think your problem start way before then, checking the logs this is where that check got introduced: Bluetooth: Fix NULL pointer dereference in smp_conn_security The l2cap_conn->smp pointer may be NULL for various valid reasons where SMP has failed to initialize properly. One such scenario is when crypto support is missing, another when the adapter has been powered on through a legacy method. The smp_conn_security() function should have the appropriate check for this situation to avoid NULL pointer dereferences. Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> Cc: stable@xxxxxxxxxxxxxxx # 4.0+ Perhaps you are missing the crypto support? -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
