We fixed this bug in version 0.5.7 of the game. Unfortunately, now the only solution is to start a new game.
OK, thanks for your quick answer. Luckily I had a forgotten save quite next to the bug, so I just had to redo from there.
