Identical fix is now also in new upstream release 1.3.2.

Reply via email to