Comment 4 for bug 1925675

Annoyingly, I have to report that this morning the display in question worked fine with both the latest stable hirsuit kernel (5.11.0-17-generic) and the version I reported the bug for (5.11.0-16-generic).

If I can find a way to reproduce it reliably, then I'll re-open this bug, but for the moment, maybe close as non-reproducible?