Comment 3 for bug 265983

There were changes in this area between 2.1.9 and 2.1.10. It is possible that the 2.1.4 fix was incomplete and the bug wasn't fully fixed until 2.1.10. I'm not certain without looking in detail whether this could be a 2.1.9 bug or may be caused by a Debian patch, but I suspect it may be a bug in 2.1.9, and if so, I think it was fixed in 2.1.10.