Andreas Enge Fri, 09 Feb 2018 13:48:07 -0800
The problem is apparently solved with the current lightning-2.1.2, closing this bug.
Andreas