Hi Chris, hrm, Jose reported this issue appearing with the stable release only (16.16.1 from his (back then) private backport fixing it), you tagged the bug as still found in 16.16.1, and I cannot see this issue at all. Unfortunately I don't know what to do with this bug. Bernhard