Correction: (In reply to C J from comment #29) > Reopening as this issued now came back after today update (11.16, so I guess > it's snapshot 11.15). The snapshot that reintroduced the bug is 20221114-0.