Comment 71 for bug 1788997

well...this bug has been unresolved for more than 6 month meanwhile, which is pretty hard for me to understand. I think it is common understanding that the Linux community is fixing bugs more or less instantaneously, as opposed to Microsoft Windows. Reverting a code change is a no brainer, which leave the question why this bug is not fixed with a kernel update. Quite a few contributers, as well as myself, have tested kernels that fix the bug, let alone, that no "official" fix has been released meanwhile. This is pretty much frustrating.

I can as well not agree that breaking a functionality completely can be considered as "medium impact"..

I mean we started out with kernel 4.15 and we're at 4.20 / 5.0 meanwhile ...