It seems the bug is fixed in upstream 5.5.4, and therefore in 5.5.4+dfsg-1. Inspecting the upstream git repository shows that the fix is included, although the upstream changelog doesn't mention it.
Furthermore, the problem no longer occurs for me with 5.5.4+dfsg-1. Best regards, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
