From: David Hotham <david.hotham@bl...> - 2011-09-11 11:25:21
I've just run into this bug, and google has directed me towards this fix - which
works just fine for me.
It doesn't look as though it has yet been committed to the codebase, though. Is
that likely to happen?