Comment 3 for bug 1389573

Revision history for this message
Nick Moffitt (nick-moffitt) wrote :

A second restart did clear it, so it may be a race in some kind of display layer management somewhere, or something to that effect.