On Tue, Mar 21, 2017 at 03:07:37PM +0200, Kristjan Koppel wrote:
(...)
> I can also confirm that this change fixes the problem for me in v1.7.3.

Thanks for confirming, it's always encouraging!

Willy

Reply via email to