https://bugzilla.kernel.org/show_bug.cgi?id=77541 --- Comment #13 from Johan Hedberg <johan.hedberg@xxxxxxxxx> --- Created attachment 138801 --> https://bugzilla.kernel.org/attachment.cgi?id=138801&action=edit Fix proposal The attached patch should fix the issue (at least it does with my Microsoft keyboard). It should be applied on top of the original patch that exposed this bug (e.g. 3.14.6). The "specialty" with this keyboard is that it seems to request authentication but not encryption when it connects. This causes a link key request/response on our side but no encryption change event. The code was incorrectly using the key_type variable (that gets set when we respond to the link key request) to determine whether we're encrypted or not, however with this keyboard this is not a reliable way to do it. Instead, we already track the real encryption state in the link_mode variable, which is what the patch changes the code to use instead of key_type. -- You are receiving this mail because: You are the assignee for the bug. -- 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
