On Wed, Aug 31, 2016 at 04:17:29PM +0200, Ludovic Courtès wrote: > I believe this is fixed by commit > d4f8884fdb897e648fd7f4262b2142d8c363ac76 (and now we have proper > tests!). > > Could you or Leo retry the previous scenario (you need to revert the > revert) and report back?
It works for me on x86_64. Thanks!