(In reply to Luciano Santos from comment #36) > It seems unlikely that was 20221114 [1], it only brought three package > updates: Ah yes, that's why I first thought that it was 20221115-0 as I updated on 11.16, but today it updated from 20221114-0 to 20221115-0. So the culprit is probably 20221112 or 20221113.