I tracked down the real culprit for this. It is fixed in v1.5.4, which
I will upload soon.

Reply via email to