Comment 3 for bug 496590

Neither of my branches (one is targetted to 2.0, the other to trunk) have landed yet, hopefully tomorrow though.

Also, for convenience, here's a shell script that reproduces. I've confirmed that both branches fix this bug.