Thanks for the workaround!
I've also reported this, a long time ago, in the days when the was an issue tracker.