A subsequent update has resolved this issue, roughly corresponding with the release of the 5.13 kernel if I remember correctly.
A subsequent update has resolved this issue, roughly corresponding with the release of the 5.13 kernel if I remember correctly.