The problem is apparently solved with the current lightning-2.1.2,
closing this bug.

Andreas




Reply via email to