version 1.1.6 should fix bug #460462 please note that according to the release announcement in URL, some user intervention is required to restore history. Maybe this could be mentioned via ewarn. Reproducible: Always
+1
amd64 stable
x86 stable. Closing.