Comment 5 for bug 35327

We fixed this "upstream", so it should be fixed with the next update.