After some testing, I determined that the bug is not present in 5.15.5+dfsg-3 but is present in 5.15.6+dfsg-1. -- Alexander Kernozhitsky