nitramred

I get the same error message – did you find any solution for this issue?

Best regards
Martin

(I did report this bug back in summer: here)