I just checked, the problem has been fixed upstream already with the 1.8.4 release from October 2009.
I just checked, the problem has been fixed upstream already with the 1.8.4 release from October 2009.