Ok, that could be of course - if the issue came in _after_ 22.04.3 got released, since the .3 was significantly tested and didn't showed that issue - but I see.
Ok, that could be of course - if the issue came in _after_ 22.04.3 got released, since the .3 was significantly tested and didn't showed that issue - but I see.