@Jack, thanks for the comment, it indeed seems the same segfault as bug #1794292 which is fixed in that update
@Jack, thanks for the comment, it indeed seems the same segfault as bug #1794292 which is fixed in that update