Comment 36 for bug 1604750

[Update] just occured on a third not quite as old computer (core2) with a siduction64 linux.
3 times update/full-upgrade did not clear the wrong "214!" (had to be "0" after the first time). It cleared after starting "apt autoremove"