I'm not 100% sure, but I think, that developers already fixed this some time ago. But probably your Image is not new enough to already contain this fix...
I'm not 100% sure too, but I am quite convinced that an image builded with source date 20090612 have to be new enought to be updated....
But the situation remains the same...