On 10-06-19 15:31, Hans de Goede wrote:
First of all this is a known issue and it seems a fix is in the works,
but what I do not understand is why the commit causing this has not
simply been reverted until the fix is done, esp. for the 5.0.x
stable series where this was introduced in 5.0.15.
The problem I'm talking about is commit d5bb334a8e17 ("Bluetooth: Align
minimum encryption key size for LE and BR/EDR connections"):
basically completely breaking all somewhat older (and some current cheap
no-name) bluetooth devices:
A revert of this was first proposed on May 22nd:
We are 18 days further now and this problem still exists, including in the
5.0.15+ and 5.1.x stable kernels.
A solution has been suggested:
and at least the Fedora 5.1.4+ kernels now carry this as a temporary fix,
but as of today I do not see a fix nor a revert in Torvald's tree yet and
neither does there seem to be any fix in the 5.0.x and 5.1.x stable series.
In the mean time we are getting a lot of bug reports about this:
And some reporters:
Are indicating that the Fedora kernels with the workaround included
still do not work...
Given that things are still broken for some users, I suggest that
for Fedora we replace the workaround with a straight forward revert
of d5bb334a8e17 for now. Also the rawhide kernels are missing the
workaround, so those are currently broken regardless.