Please note that it's 2.0, not 2.11.

It happens to be the 11th beta release of the upcoming 2.0, but it's not 2.11. This is notated as 2.0b11, not 2.11b. I know this is getting picky with semantics, but it's important for posterity here on the BBS. (For people looking up old posts next year sometime. )

This is a known bug in 2.0b11. It's been there since 2.0b3, and we're a little worried about it because they haven't found its cause yet.