Usually, I don't object to having each issue have its own bug, but this is really the same bug as 34893. 34893 is so messed up that this issue will go away when that is fixed. *** This bug has been marked as a duplicate of 34893 ***
Looks like the same bug all right. It works for me when the other one does and fails when the other one fails. Verifying.