Comment 4 for bug 493101

That's fixed upstream now.