So far, I can reliably reproduce the error on 6.16.3-1, and now also 6.16.7-1.

Philipp

Reply via email to