Yes.. I'm a little confused. For example the previously mentioned thread (id=215167) is still very much ongoing, with some people reporting that certain kernel versions fix this and others reporting it showing up in regressions as late as 6.2.
They referenced a message https://<email address hidden>/ refers to commit 95655456e7cee858a23793f67025765b4c4c227b upstream, which was merged into 5.16 mainline last year. https://lkml.org/lkml/2022/1/14/195 -- I will post back in the bugzilla thread later that this seems to be unrelated.
I believe on the Ubuntu side patching from 5.11 to 5.15 caused this problem for me. And it would appear that 5.19 has it as well. But needless to say in "stable LTS" (22.04.2/5.15) this is still happening, breaking bluetooth for Ubuntu users.
Yes.. I'm a little confused. For example the previously mentioned thread (id=215167) is still very much ongoing, with some people reporting that certain kernel versions fix this and others reporting it showing up in regressions as late as 6.2.
They referenced a message https://<email address hidden>/ refers to commit 95655456e7cee85 8a23793f6702576 5b4c4c227b upstream, which was merged into 5.16 mainline last year. https:/ /lkml.org/ lkml/2022/ 1/14/195 -- I will post back in the bugzilla thread later that this seems to be unrelated.
I believe on the Ubuntu side patching from 5.11 to 5.15 caused this problem for me. And it would appear that 5.19 has it as well. But needless to say in "stable LTS" (22.04.2/5.15) this is still happening, breaking bluetooth for Ubuntu users.