Hello. This issue seems fixed as of version 2.5.8-1.
However, it is still an issue in trixie. Before closing the bug: Would you please help me to determine how exactly it was fixed? I'd like to see a fix in trixie, even if that means taking care of the related release.debian.org bureaucracy myself. I explained the way to reproduce it in the initial bug report, and, as always, I can offer a VM to reproduce if the information I provided was not enough. Thanks.
