What in the 2.5.9-5 changelog fixes this bug? I can see that the bug is still open in Debian & the maintainer didn't claim it fixed the bug.
What in the 2.5.9-5 changelog fixes this bug? I can see that the bug is still open in Debian & the maintainer didn't claim it fixed the bug.